Re: Upper limit arguments of pg_logical_slot_xxx_changes functions accept invalid values

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Upper limit arguments of pg_logical_slot_xxx_changes functions accept invalid values
Date: 2018-07-26 22:27:29
Message-ID: 20180726222729.GB1754@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-07-26 22:30:50 Re: pgbench: improve --help and --version parsing
Previous Message Fabien COELHO 2018-07-26 22:22:16 Re: pgbench: improve --help and --version parsing