| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>, Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org, Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
| Subject: | Re: BUG #18170: Unexpected error: no relation entry for relid 3 |
| Date: | 2023-10-28 07:31:19 |
| Message-ID: | 3fdf9a41-c0a9-4b09-bfba-0133e28bed8d@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 28/10/2023 08:59, Andrei Lepikhov wrote:
>> BTW, I'm a little surprised that QTW_DONT_COPY_QUERY doesn't seem to be
>> used anywhere currently.
>
> I too. But we use this flag in the enterprise fork to reduce memory
> consumption. It could be proposed for upstream, but looks a bit unsafe.
> I guess, some extensions could do the same.
What is "the enterprise fork"? This is a PostgreSQL mailing list.
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2023-10-28 07:56:15 | Re:BUG #18172: High memory usage in tSRF function context |
| Previous Message | Andrei Lepikhov | 2023-10-28 06:59:23 | Re: BUG #18170: Unexpected error: no relation entry for relid 3 |