Re: postgres_fdw and skip locked

From: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: postgres_fdw and skip locked
Date: 2022-02-16 15:08:30
Message-ID: 13e6be2feccfd14e23259355837d18e1@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ashutosh Bapat писал 2022-02-16 16:40:
> On Mon, Feb 14, 2022 at 4:23 PM Alexander Pyhalov
> <a(dot)pyhalov(at)postgrespro(dot)ru> wrote:
>>
>> Hi.
>>
>> Now select ... for update ... [skip locked|nowait] options are not
>> pushed down to remote servers. I see the only reason is that we can
>> speak to pre-9.5 server, which doesn't understand skip locked option.
>> Are there any other possible issues? Should we add foreign table
>> option
>> to control this behavior?
>
> Should we always push these clauses if remote server's version is
> newer than 9.5? There are quite a few options already. It will be good
> not to add one more.
>
> I see that these options will work for all kinds of relations. So no
> problem if foreign table is pointing to something other than a table.

Hi.
The issue is that we perform deparsing while planing, we haven't
connected to server yet.
Are there any ideas how to find out its version without specifying it,
for example, in server options?
--
Best regards,
Alexander Pyhalov,
Postgres Professional

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-02-16 15:40:01 Re: adding 'zstd' as a compression algorithm
Previous Message Pavel Stehule 2022-02-16 15:04:35 Re: support for CREATE MODULE