| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lukáš Sobotka <sobotka(dot)luk(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Trouble with postgres_fdw & dblink extensions |
| Date: | 2018-11-15 23:45:21 |
| Message-ID: | 3232.1542325521@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?UTF-8?B?THVrw6HFoSBTb2JvdGth?= <sobotka(dot)luk(at)gmail(dot)com> writes:
> I would be grateful for some help. I am writing you because I am confused
> about using data foreign wrappers and dblink. I attached simplified script
> describing the problem.
I think what is happening is that postgres_fdw starts a transaction on
its connection as soon as it's asked to do something, and then the CREATE
TABLE executed on dblink's separate connection isn't visible to that
already-in-progress transaction.
That theory only holds up if you are running in serializable mode (which
postgres_fdw would then also use for its remote transaction). Which you
didn't say, but it's hard to see how it'd fail otherwise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-11-16 00:14:51 | Re: Trouble with postgres_fdw & dblink extensions |
| Previous Message | Lukáš Sobotka | 2018-11-15 23:23:41 | Trouble with postgres_fdw & dblink extensions |