Postgres Pro
Downloads
Home   >   mailing lists

Re: Upper limit arguments of pg_logical_slot_xxx_changes functionsaccept invalid values - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Upper limit arguments of pg_logical_slot_xxx_changes functionsaccept invalid values
Date
Msg-id 20180726222729.GB1754@paquier.xyz
Whole thread Raw
In response to Upper limit arguments of pg_logical_slot_xxx_changes functions acceptinvalid values  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Upper limit arguments of pg_logical_slot_xxx_changes functionsaccept invalid values  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Tree view 
On Thu, Jul 12, 2018 at 09:58:16AM +0900, Masahiko Sawada wrote:
>   If upto_lsn is non-NULL, decoding will include only those
> transactions which commit prior to the specified LSN. If upto_nchanges
> is non-NULL, decoding will stop when the number of rows produced by
> decoding exceeds the specified value.

It is also possible to interpret a negative value as an equivalent to
infinite, no?  That's how I read the documentation quote you are adding
here.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: pgbench: improve --help and --version parsing
Next
From: Michael Paquier
Date:
Subject: Re: pgbench: improve --help and --version parsing