Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures
От
Michael Paquier
Тема
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures
Дата
Msg-id
Y41v42wAFdePvQhg@paquier.xyz
Ответ на
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures (Bharath Rupireddy)
Список
Дерево обсуждения
Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Nathan Bossart <nathandbossart@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Nathan Bossart <nathandbossart@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Maxim Orlov <orlovmg@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Michael Paquier <michael@paquier.xyz>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Michael Paquier <michael@paquier.xyz>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Michael Paquier <michael@paquier.xyz>
Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures Maxim Orlov <orlovmg@gmail.com>
On Mon, Dec 05, 2022 at 08:48:25AM +0530, Bharath Rupireddy wrote: > So, a SQL function pg_dissect_walfile_name (or some other better name) > given a WAL file name returns the tli and seg number. Then the > pg_walfile_offset_lsn can just be a SQL-defined function (in > system_functions.sql) using this new function and pg_settings. If this > understanding is correct, it looks good to me at this point. I would do without the SQL function that looks at pg_settings, FWIW. > That said, let's also hear from others. Sure. Perhaps my set of suggestions will not get the majority, though.. -- Michael
В списке pgsql-hackers по дате отправления