Re: Libpq support to connect to standby server as priority

From: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
To: Greg Nancarrow <gregn4422(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, "Smith, Peter" <peters(at)fast(dot)au(dot)fujitsu(dot)com>, David Steele <david(at)pgmasters(dot)net>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)fujitsu(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Dave Cramer <pg(at)fastcrypt(dot)com>, Jing Wang <jingwangian(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Elvis Pranskevichus <elprans(at)gmail(dot)com>
Subject: Re: Libpq support to connect to standby server as priority
Date: 2020-11-24 12:26:08
Message-ID: 91749879-e086-02db-a4dd-44d49f0332b2@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.09.2020 10:57, Greg Nancarrow wrote:
> Thanks for your thoughts, patches and all the pointers.
> I'll be looking at all of them.
> (And yes, the comma instead of bitwise OR is of course an error,
> somehow made and gone unnoticed; the next field in the struct is an
> enum, so accepts any int value).
>
> Regards,
> Greg Nancarrow
> Fujitsu Australia
>
CFM reminder.

Hi, this entry is "Waiting on Author" and the thread was inactive for a
while. As far as I see, the patch needs some further work.
Are you going to continue working on it, or should I mark it as
"returned with feedback" until a better time?

--
Anastasia Lubennikova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2020-11-24 12:32:45 Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Previous Message Anastasia Lubennikova 2020-11-24 12:11:53 Re: pgbench and timestamps (bounced)