| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: list of TransactionIds |
| Date: | 2022-05-14 09:45:45 |
| Message-ID: | CAA4eK1+J5MgNYWvJdogK2_+9pPni8fQ1czO38LOdsPnrFrch+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 14, 2022 at 1:57 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> We didn't have any use of TransactionId as members of List, until
> RelationSyncEntry->streamed_txns was introduced (464824323e57, pg14).
> It's currently implemented as a list of int. This is not wrong at
> present, but it may soon be, and I'm sure it rubs some people the wrong
> way.
>
> But is the rubbing way wrong enough to add support for TransactionId in
> pg_list.h, including, say, T_XidList?
>
+1. I don't know if we have a need for this at other places but I feel
it is a good idea to make its current use better.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2022-05-14 13:32:54 | Re: Skipping schema changes in publication |
| Previous Message | Japin Li | 2022-05-14 08:49:22 | Re: Backends stunk in wait event IPC/MessageQueueInternal |