| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | nadav(at)tailorbrands(dot)com |
| Cc: | pgpool-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal: recent access based routing for primary-replica setups |
| Date: | 2025-09-09 00:39:44 |
| Message-ID: | 20250909.093944.156562835222886259.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-hackers |
Hi Nadav,
> Hi Tatsuo,
>
> Please find attached the 3 patch files (implementation, tests, docs) with
> the updates we discussed.
>
> What do you think?
I haven't read the code details yet but I have a few questions.
1) Can we use only replication_delay_source_cmd and if it's value is
'builtin', then we treat it as replication_delay_source = builtin?
Maybe this is matter of taste but I would like to know your
opinion.
2) replication_delay_source_cmd will be given an ordered list of
instance identifiers. But it seems there's no way for the command
which one is the primary instance. Is it okay for the command?
3) Why do you have 3 kind of instance identifiers (application name,
hostname (IP) + port and node id? I thought "hostname (IP) + port"
is sufficient.
Comments?
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nadav Shatz | 2025-09-15 12:48:07 | Re: Proposal: recent access based routing for primary-replica setups |
| Previous Message | Tatsuo Ishii | 2025-09-08 12:02:52 | Re: Proposal: recent access based routing for primary-replica setups |