| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Maxim Orlov <orlovmg(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add 64-bit XIDs into PostgreSQL 15 |
| Date: | 2022-01-07 05:18:30 |
| Message-ID: | fd283f0e-af48-b7c1-a286-83c6a43b6a57@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022/01/06 19:24, Simon Riggs wrote:
> On Thu, 30 Dec 2021 at 13:19, Maxim Orlov <orlovmg(at)gmail(dot)com> wrote:
>
>> Your opinions are very much welcome!
>
> This is a review of the Int64 options patch,
> "v6-0001-Add-64-bit-GUCs-for-xids.patch"
Do we really need to support both int32 and int64 options? Isn't it enough to replace the existing int32 option with int64 one? Or how about using string-type option for very large number like 64-bit XID, like it's done for recovery_target_xid?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | torikoshia | 2022-01-07 05:30:37 | Re: RFC: Logging plan of the running query |
| Previous Message | tanghy.fnst@fujitsu.com | 2022-01-07 05:17:21 | RE: Support tab completion for upper character inputs in psql |