| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Langote <amitlangote09(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Subject: | Re: The documentation for READ COMMITTED may be incomplete or wrong |
| Date: | 2023-05-19 18:42:50 |
| Message-ID: | CAJ7c6TPkG+S2GTOr+k=BCYQJQXApD_HvA9tx+4AKU-ZsiY3cHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Tom,
> Done that way. I chose to replace the tuple_table field, because
> it was in a convenient spot and it seemed like the field least
> likely to have any outside code referencing it.
Many thanks!
If it's not too much trouble could you please recommend good entry
points to learn more about the internals of this part of the system
and accompanying edge cases? Perhaps there is an experiment or two an
extension author can do in order to lower the entry threshold and/or
known bugs, limitations or wanted features one could start with?
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2023-05-19 19:13:47 | Re: Order changes in PG16 since ICU introduction |
| Previous Message | Tom Lane | 2023-05-19 18:33:36 | Re: The documentation for READ COMMITTED may be incomplete or wrong |