| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Prevent COPY FREEZE on Foreign tables |
| Date: | 2025-02-03 21:05:44 |
| Message-ID: | CAA5RZ0uNSgMpQLE6Cf85=p7WZPw+6s5bUEgjuoXGPpWQGT34kA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Unless there's some existing way to specify a FREEZE option in the FDW API
> (I assume there isn't), I agree with this.
I am not aware of any way to do this either as postgres_fdw is simply
using libpq.
> > I was also looking at why we block a parent from COPY FREEZE[1], but
> Commit 5c9a551 and its thread [0] appear to have some additional details
> about this.
>
> [0] https://postgr.es/m/CAKJS1f9BbJ%2BFY3TbdCiap3qXHTFOiwtays9s36-oQkkM9_R5bg%40mail.gmail.com
Thanks for the thread. I will go through it.
I did not too much investigation here yet but I can imagine this might
be a worthwhile
to see the possibility to remove this limitation on a partitioned table.
Regards,
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-02-03 21:08:03 | Re: Better title output for psql \dt \di etc. commands |
| Previous Message | Nathan Bossart | 2025-02-03 20:48:34 | Re: Prevent COPY FREEZE on Foreign tables |