PostgreSQL: select different column instead of ID for Bookmark

Tags: PostgreSQL

#1 seckindemir

Hello,

I have installed NXLog community edition to collect table data from PostgreSQL database but, the table isn't contain an ID column. As I understand, NXLog required to this field to bookmark but, we don't have. I'm looking for a workaround to solve the issue. On the other hand I can see a workaround from the following link and we can configure the ID with select statements but, the article isn't about the PostgreSQL. Could you please someone help me for PostgreSQL?

https://nxlog.co/documentation/nxlog-user-guide/mssql.html

the second question: Can we define a specific column (such as eventime) for ID (bookmark) with the following sample data?

2020-02-11 15:00:00.0000 2020-02-11 15:00:01.0001 2020-02-11 15:00:02.0002 2020-02-11 15:00:03.0000

Thanks in Advance!

Best Regards

SD

#2 ArkadiyDeactivated Nxlog ✓
#1 seckindemir
Hello, I have installed NXLog community edition to collect table data from PostgreSQL database but, the table isn't contain an ID column. As I understand, NXLog required to this field to bookmark but, we don't have. I'm looking for a workaround to solve the issue. On the other hand I can see a workaround from the following link and we can configure the ID with select statements but, the article isn't about the PostgreSQL. Could you please someone help me for PostgreSQL? https://nxlog.co/documentation/nxlog-user-guide/mssql.html the second question: Can we define a specific column (such as eventime) for ID (bookmark) with the following sample data? 2020-02-11 15:00:00.0000 2020-02-11 15:00:01.0001 2020-02-11 15:00:02.0002 2020-02-11 15:00:03.0000 Thanks in Advance! Best Regards SD

Hello,

Just to be sure that we are looking in the same manual please take a note that we have different manual for Community Edition of NXLog, here is the link: https://nxlog.co/docs/nxlog-ce/nxlog-reference-manual.html

Regarding your workaround - if we got your idea right and you thinking about use event_time column it's not really good idea because values in this field isn't always unique and they can't replace ID's completely.

And could you share you config with us? It will make things much easier.

Best regards, Arch