nce to our customers, but their postgres database itself is
absolutely mission critical.
Thanks,
Meel
On Wed, Sep 20, 2017 at 12:43 AM Michael Paquier
wrote:
> On Wed, Sep 20, 2017 at 3:14 PM, Meel Velliste wrote:
> > From what I understand about logical decoding, there is no limit to
>From what I understand about logical decoding, there is no limit to how
many log entries will be retained by the server if nobody reads them from
the logical slot. This means that a client that fails to read from the slot
has the power to bring down the master database because the server's disk
wi
I would like to use the "xmax" column to detect rows that have been
recently deleted. Is it possible to get the deleted row versions with
non-zero xmax to remain visible long enough that I could periodically
check, say once an hour, and still be able to see rows that were deleted
since I last check
My goal is to select rows that are new or have been modified since a given
snapshot. I am doing it like this:
SELECT * FROM my_table WHERE NOT
txid_visible_in_snapshot(xmin::TEXT::BIGINT,
'123456:123456:'::TXID_SNAPSHOT);
On one hand, it seems to me that the txid_visible_in_snapshot function was
