| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 花田 茂 <shigeru(dot)hanada(at)gmail(dot)com> |
| Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FDW for PostgreSQL |
| Date: | 2012-11-07 02:57:44 |
| Message-ID: | 26340.1352257064@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?iso-2022-jp?B?GyRCMlZFRBsoQiAbJEJMUBsoQg==?= <shigeru(dot)hanada(at)gmail(dot)com> writes:
> ClassifyConditions creates new lists, local_conds and remote_conds,
> which have cells which point RestrictInfo(s) in baserestrictinfo.
> It doesn't copy RestrictInfo for new lists, but I think it's ok
> because baserestrictinfo list itself and RestrictInfo(s) pointed by
> it are never modified by postgresql_fdw.
That's good. I think there are actually some assumptions that
RestrictInfo nodes are not copied once created. You can link them into
new lists all you want, but don't copy them.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-11-07 04:19:06 | Re: Proposal for Allow postgresql.conf values to be changed via SQL |
| Previous Message | 花田 茂 | 2012-11-07 02:52:56 | Re: FDW for PostgreSQL |