Re: pg_walfile_name_offset can return inconsistent values
От
Jehan-Guillaume de Rorthais
Тема
Re: pg_walfile_name_offset can return inconsistent values
Дата
Msg-id
20190726113019.0a3b34c7@firost
Ответ на
pg_walfile_name_offset can return inconsistent values (Kyotaro Horiguchi)
Список
Дерево обсуждения
pg_walfile_name_offset can return inconsistent values Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_walfile_name_offset can return inconsistent values Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Re: pg_walfile_name_offset can return inconsistent values Bruce Momjian <bruce@momjian.us>
Re: pg_walfile_name_offset can return inconsistent values Matthias van de Meent <boekewurm+postgres@gmail.com>
Re: pg_walfile_name_offset can return inconsistent values Bruce Momjian <bruce@momjian.us>
Re: pg_walfile_name_offset can return inconsistent values Andres Freund <andres@anarazel.de>
Re: pg_walfile_name_offset can return inconsistent values Michael Paquier <michael@paquier.xyz>
Re: pg_walfile_name_offset can return inconsistent values Bruce Momjian <bruce@momjian.us>
Re: pg_walfile_name_offset can return inconsistent values Andres Freund <andres@anarazel.de>
Re: pg_walfile_name_offset can return inconsistent values Bruce Momjian <bruce@momjian.us>
Re: pg_walfile_name_offset can return inconsistent values Bruce Momjian <bruce@momjian.us>
Re: pg_walfile_name_offset can return inconsistent values Michael Paquier <michael@paquier.xyz>
Re: pg_walfile_name_offset can return inconsistent values Bruce Momjian <bruce@momjian.us>
On Fri, 26 Jul 2019 17:21:20 +0900 (Tokyo Standard Time)
Kyotaro Horiguchi wrote:
> Hello.
>
> While looking [1], I noticed that pg_walfile_name_offset behaves
> somewhat oddly at segment boundary.
>
> select * from (values ('0/16ffffff'), ('0/17000000'), ('0/17000001')) as
> t(lsn), lateral pg_walfile_name_offset(lsn::pg_lsn);
> lsn | file_name | file_offset
> ------------+--------------------------+-------------
> 0/16ffffff | 000000020000000000000016 | 16777215
> 0/17000000 | 000000020000000000000016 | 0
> 0/17000001 | 000000020000000000000017 | 1
>
>
> The file names are right as defined, but the return value of the
> second line wrong, or at least misleading.
+1
I noticed it as well and put this report on hold while working on my patch.
Thanks for reporting this!
> It should be (16, 1000000) or (16, FFFFFF). The former is out-of-domain so we
> would have no way than choosing the latter. I'm not sure the purpose of
> the second output parameter, thus the former might be right
> decision.
>
> The function returns the following result after this patch is
> applied.
>
> select * from (values ('0/16ffffff'), ('0/17000000'), ('0/17000001')) as
> t(lsn), lateral pg_walfile_name_offset(lsn::pg_lsn);
> lsn | file_name | file_offset
> ------------+--------------------------+-------------
> 0/16ffffff | 000000020000000000000016 | 16777214
> 0/17000000 | 000000020000000000000016 | 16777215
> 0/17000001 | 000000020000000000000017 | 0
So you shift the file offset for all LSN by one byte? This could lead to
regression in various tools relying on this function.
Moreover, it looks weird as the LSN doesn't reflect the given offset anymore
(FFFFFF <> 16777214, 000001 <> 0, etc).
Another solution might be to return the same result when for both 0/16ffffff and
0/17000000, but it doesn't feel right either.
So in fact, returning 0x1000000 seems to be the cleaner result to me.
Regards,
В списке pgsql-hackers по дате отправления
От: Kyotaro Horiguchi
Дата:
От: Ashutosh Sharma
Дата: