| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Biryukov <79166341370(at)yandex(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: posgres 12 bug (partitioned table) |
| Date: | 2020-08-11 17:13:18 |
| Message-ID: | CA+Tgmob1xt7b5gn0s_D2TvDsJ84+Ek9_q_+8W6Xqu5Q9D-M85w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Tue, Aug 11, 2020 at 12:02 PM Pavel Biryukov <79166341370(at)yandex(dot)ru> wrote:
> I just want to point that Npgsql provider for .Net Core builds queries like that (RETURNING xmin) to keep track for concurrency.
> This bug stops us from moving to partitioned tables in Postgres 12 with Npgsql.
That's certainly a good reason to try to make it work. And we can make
it work, if we're willing to assume that everything's a heap table.
But at some point, that hopefully won't be true any more, and then
this whole idea becomes pretty dubious. I think we shouldn't wait
until it happens to start thinking about that problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-08-11 17:22:41 | Re: posgres 12 bug (partitioned table) |
| Previous Message | Pavel Biryukov | 2020-08-11 16:02:57 | Re: posgres 12 bug (partitioned table) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-08-11 17:22:41 | Re: posgres 12 bug (partitioned table) |
| Previous Message | James Coleman | 2020-08-11 16:53:30 | Re: massive FPI_FOR_HINT load after promote |