xtdb 2023-05-08 | Slack Archive

hifumi12301:05:35

Is XTDB suited for use cases where I’d like to store “small” (< 500 characters), immutable, plaintext documents with metadata? This is my first time I am attempting to use a non-SQL database, so I want to make sure I am not setting myself up for improper use of XTDB 😄

tatut03:05:44

sure, I don’t see why not

➕ 1

tatut03:05:05

depending on how you want to search them, you may want to setup the lucene index as well to enable full text search

👍 2

Jesse18:05:49

Does anyone know if it is possible to use XTDB using Postgres with pgbouncer? When I try it I'm seeing errors like ERROR: prepared statement "S_1" already exists when ingesting transactions, so I'm thinking pgbouncer is not supported

refset08:05:30

Hi @U03MWJ46V0Q I don't think we intended for pgbouncer to not work so it's probably a bug. Can you describe how you tested this?

Jesse08:05:32

Hi @U899JBRPF, thanks for the reply! I only tried to put pgbouncer in front of my Postgres and connected XTDB to it. The XTDB logs would show the above error while building the index (with different values for "S_1"). Good to know this isn't intentional; I can probably make it work with one of the https://stackoverflow.com/questions/7611926/postgres-error-prepared-statement-s-1-already-exists Disabling prepared statements in JDBC sounds risky, but I'll try switching to Session pooling (screenshot attached from the DigitalOcean pgbouncer config)

refset13:05:47

Interesting :thinking_face: yeah I would be surprised if none of those suggested workarounds could be made to work. Thanks for sharing the info 🙏

2023-05-08

Channels