From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
cc: Swathi P <swathi.bluepearl@gmail.com>, pgsql-general@lists.postgresql.org
Subject: Re: Query on postgres_fdw extension
In-reply-to: 
 <CALj2ACX6YarPvhXmGkVfZJZxLfAh=W+Pfub2FfKVH_5dQ0rgwQ@mail.gmail.com>
References: 
 <CAKtL=nkXe1zXK5SMcqnzDpCON+CUPHdnjJZfZonwYQa0BDkCGQ@mail.gmail.com>
 <CALj2ACUejnxHERB4QNvKV3qVW4VQ=a8Y+kuuPTseuwq0prVe3Q@mail.gmail.com>
 <CAKtL=n=OND+AYqztr57Njanj8M9iyy6uvfmp1yX2Zgk164Ejww@mail.gmail.com>
 <1883853.1621003992@sss.pgh.pa.us>
 <CALj2ACX6YarPvhXmGkVfZJZxLfAh=W+Pfub2FfKVH_5dQ0rgwQ@mail.gmail.com>
Comments: In-reply-to Bharath Rupireddy
 <bharath.rupireddyforpostgres@gmail.com>
	message dated "Fri, 14 May 2021 20:40:52 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1885557.1621006361.1@sss.pgh.pa.us>
Date: Fri, 14 May 2021 11:32:41 -0400
Message-ID: <1885558.1621006361@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1885558.1621006361%40sss.pgh.pa.us>
Precedence: bulk

Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> On Fri, May 14, 2021 at 8:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> One conceivable workaround is to do your insertions through a
>> foreign table that doesn't even have the serial column, so that
>> the INSERT command received by the remote server lacks that
>> column and the default gets applied.  Probably too messy though.

> Then the serial column cannot be selected via the foreign table.

Yeah, you'd probably need to use different tables for inserting
and reading, which is why I called it messy.

The idea you pointed to in Michael's blog might work though,
ie make a local function that reaches over to the remote server
to get a globally-valid next sequence value, and use that as
the default expression of the foreign table.

			regards, tom lane