| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | guxiaobo1982 <guxiaobo1982(at)qq(dot)com> |
| Cc: | Jov <amutu(at)amutu(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Reply: Can we specify transaction level when connectting toexternal postgresql server via postgres_fdw |
| Date: | 2013-07-16 05:57:36 |
| Message-ID: | 939.1373954256@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"=?gb18030?B?Z3V4aWFvYm8xOTgy?=" <guxiaobo1982(at)qq(dot)com> writes:
> It works for insert and select statement under serializable level, but it seems update/delete statements are not support, is that true?
> template1=# update user_info set info='1234' where id=102;
> ERROR: DECLARE CURSOR ... FOR UPDATE/SHARE is not supported
> DETAIL: Cursors must be READ ONLY.
The postgres_fdw documentation says
postgres_fdw can be used with remote servers dating back to
PostgreSQL 8.3. Read-only capability is available back to 8.1.
I don't recall exactly when Greenplum forked off from Postgres, but
8.1 or so wouldn't surprise me. The quoted error message looks about
like what you'd get when trying to use postgres_fdw with a pre-8.3
remote server.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | guxiaobo1982 | 2013-07-16 06:52:16 | Reply: Reply: Can we specify transaction level when connectting toexternal postgresql server via postgres_fdw |
| Previous Message | shankar.kotamarthy@gmail.com | 2013-07-16 05:35:41 | Re: pg_upgrade could not create catalog dump while upgrading from 9.0 to 9.2 |