Re: concerns around pg_lsn

From: Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: concerns around pg_lsn
Date: 2019-08-04 03:41:09
Message-ID: CAOgcT0NeMFPf1QXNbVcJ7iDHjBB8t5S5qLhOTpRwWOA=+ScjxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sure Michael, in the attached patch I have reverted the checks from
pg_lsn_in_internal() and added Assert() per my original patch.

Regards,
Jeevan Ladhe

Attachment Content-Type Size
0001-Make-have_error-initialization-more-defensive-v2.patch application/octet-stream 4.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-08-04 03:57:01 Re: concerns around pg_lsn
Previous Message Peter Geoghegan 2019-08-04 03:25:03 Re: The unused_oids script should have a reminder to use the 8000-8999 OID range