From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Robert Haas' <robertmhaas(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <pg(at)fastcrypt(dot)com>, Jing Wang <jingwangian(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Libpq support to connect to standby server as priority |
Date: | 2019-03-20 06:01:11 |
Message-ID: | 0A3221C70F24FB45833433255569204D1FBE249B@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: Robert Haas [mailto:robertmhaas(at)gmail(dot)com]
> I really dislike having both target_sesion_attrs and
> target_server_type. It doesn't solve any actual problem. master,
> slave, prefer-save, or whatever you like could be put in
> target_session_attrs just as easily, and then we wouldn't end up with
> two keywords doing closely related things. 'master' is no more or
> less a server attribute than 'read-write'.
Hmm, that may be OK. At first, I felt it strange to treat the server type (primary or standby) as a session attribute. But we can see the server type as one attribute in a sense that a session is established for. I'm inclined to agree with:
target_session_attr = {any | read-write | read-only | prefer-read | primary | standby | prefer-standby}
Regards
Takayuki Tsunakawa
From | Date | Subject | |
---|---|---|---|
Next Message | Iwata, Aya | 2019-03-20 06:15:38 | RE: [PATCH] get rid of StdRdOptions, use individual binary reloptions representation for each relation kind instead |
Previous Message | Andrey Borodin | 2019-03-20 05:55:51 | Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line |