Re: dblink_build_sql_update versus dropped columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: dblink_build_sql_update versus dropped columns
Date: 2010-06-14 18:54:57
Message-ID: 17377.1276541697@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> I didn't even think people were using those functions for many years
> since I never heard any complaints. I'd say better to not backpatch
> changes to logical ordering, but FWIW the attached at least fixes the
> immediate bug in head and ought to work at least a few branches.

[squint...] This doesn't appear to me to fix the problem. You really
need the query-construction loops to track logical and physical numbers
separately.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2010-06-14 18:58:49 Re: dblink_build_sql_update versus dropped columns
Previous Message Bruce Momjian 2010-06-14 18:48:24 Re: Typo in plperl doc ?