Re: Option to dump foreign data in pg_dump

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: Luis Carril <luis(dot)carril(at)swarm64(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: Option to dump foreign data in pg_dump
Date: 2019-09-24 06:25:01
Message-ID: CALAY4q9P=PmuHv8bA+s22RZUPj1RJAhU3qLXnjM7oT5iFZcfnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 20, 2019 at 6:20 PM Luis Carril <luis(dot)carril(at)swarm64(dot)com> wrote:

> Hello,
> thanks for the comments!
>
> * + if (tdinfo->filtercond || tbinfo->relkind == RELKIND_FOREIGN_TABLE)
>
> filter condition is not implemented completely yet so the logic only work
> on foreign table so I think its better to handle it separately
>
> Note that there is another if condition that actually applies the the
> filtercondition if provided, also for a we need to do a COPY SELECT instead
> of a COPY TO
>

but we can't supplied where clause in pg_dump yet so filtercondtion is
always NULL and the logic became true only on foreign table.

> * I don’t understand the need for changing SELECT query .we can use the
> same SELECT query syntax for both regular table and foreign table
>
> To which query do you refer? In the patch there are three queries: 1
> retrieves foreign servers, another is the SELECT in the COPY that now it
> applies in case of a filter condition of a foreign table, and a third that
> retrieves the oid of a given foreign server.
>
>
SELECT on COPY

regards
Surafel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2019-09-24 06:25:08 Re: Cache lookup errors with functions manipulation object addresses
Previous Message Kyotaro Horiguchi 2019-09-24 05:48:16 Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node