Re: Redacting params in PostgreSQL logs

2018-03-30 Thread Vijaykumar Jain
https://github.com/lfittl/pg_query/blob/master/README.md#parsing-a-normalized-query OK found this :) Regards, Vijay From: Vijaykumar Jain Sent: Friday, March 30, 2018 11:24:30 PM To: pgsql-general@lists.postgresql.org Subject: Redacting params in PostgreSQL logs

Redacting params in PostgreSQL logs

2018-03-30 Thread Vijaykumar Jain
Hi, I have a project of sending postgres logs to ELK stack. It is working fine. Now there are concerns that logs have query statements with parameters. and then GDPR and other PII issues. Is there a way I can redact the params in statements in the logs by some config or extension ? Pls note: I

Re: dblink: could not send query: another command is already in progress

2018-03-30 Thread Thiemo Kellner
On 03/30/18 11:14, Laurenz Albe wrote: You have to consume the result before you can send the next query. I changed implementation but still get the same error but now different context. I tried to retrieve the result but I failed I committed the last code to its project repository at Source

Schema-based replication

2018-03-30 Thread Moreno Andreo
Hi folks:-) I'm about to design and develop a cross-platform schema-based replicator as a module for an app scheduled for alpha in the next mid-fall/winter. Before digging into it I need to know if I'm reinventing the wheel or not, but AFAIK pglogical can't give this kind of granularity, especi

Re: Asynchronous Trigger?

2018-03-30 Thread Adam Tauno Williams
On Thu, 2018-03-29 at 22:29 +, Cory Tucker wrote: > Is it possible to have the execution of a trigger (or any function) > not block the completion of the statement they are associated with? > A pattern I had hoped to implement was to do a quick update of rows > that signaled they needed attenti

Re: Question about buffers_alloc in pg_stat_bgwriter view for monitoring

2018-03-30 Thread Achilleas Mantzios
On 29/03/2018 20:24, Alvar Freude wrote: Hi, Am 29.03.2018 um 10:30 schrieb Gunnar Nick Bluth : Thus, buffer_alloc is the global count of buffers allocated in the cluster. That it appears in the bgwriter statistics is more or less coincidental. But it seems not to be the total shared_buffers

Re: dblink: could not send query: another command is already in progress

2018-03-30 Thread Laurenz Albe
Thiemo Kellner wrote: > The cause of the error message is clear; as the documentation says: > > >the query will fail soon. You must still complete the normal query > > protocol, > >for example by calling dblink_get_result. > > Ah, maybe this is the underlying problem. If dblink requires

Re: dblink: could not send query: another command is already in progress

2018-03-30 Thread Thiemo Kellner
On 03/30/18 07:39, Laurenz Albe wrote: psql:testing/test.pg_sql:41: NOTICE: Connection busy: 1 psql:testing/test.pg_sql:41: NOTICE: Last error: OK psql:testing/test.pg_sql:41: NOTICE: Cancel query: OK psql:testing/test.pg_sql:41: NOTICE: Connection busy: 0 psql:testing/test.pg_sql:41: NOT