global variable KEYWORD_INDEX_NAME in PgvectorDocumentStore avoids multiple tables

[MartinMayoIglesias]

Hello, I noticed that the index (KEYWORD_INDEX_NAME) associated to a table in PgvectorDocumentStore (Haystack 2.0) is defined as global and later in the code it seems to raise an exception when one tries to create a second table, and as a consequence only one table per database can be used. Was it intentionally? What do you recommend me in case I need to use different tables to store data in order to be used to, for example, talk-to-documents?

Just in case, the exception is:
"haystack.document_stores.errors.errors.DocumentStoreError: Could not create keyword index on table."

[anakin87]

I think this has just been fixed by deepset-ai/haystack-core-integrations#818

Can you try updating the package and see if it works?

[goncafab]

Using haystack-ai = "2.2.3" and pgvector-haystack = "0.4.0", and manually setting both hnsw_index_name and keyword_index_name for each table, I can confirm that it works.

[touhi99]

Using haystack-ai = "2.2.3" and pgvector-haystack = "0.4.0", and manually setting both hnsw_index_name and keyword_index_name for each table, I can confirm that it works.

Thanks! that saved me!