| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Swathi P <swathi(dot)bluepearl(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query on postgres_fdw extension |
| Date: | 2021-06-01 10:01:57 |
| Message-ID: | CAPmGK14odzTd8JR7_wuVe81K111+7qAWBRXCwjKd7NrGij0Fbw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Hi,
On Fri, May 14, 2021 at 6:08 PM Swathi P <swathi(dot)bluepearl(at)gmail(dot)com> wrote:
> In our sharding solution, we have multiple coodinator nodes. If we declare the table column as serial data type, we might end up having duplicate values for id column in the table_a in host_b (data node) as cconnections come from multiple coordinatoor nodes and might end up in duplicate key violations.
>
> Hence we decided to have the coordinator nodes as stateless and hence declared the column with no serial/sequence. Let me know if this makes sense.
It seems reasonable to me to make coodinator nodes stateless, but may
I ask the reason you use multiple coordinator nodes?
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-06-01 10:24:31 | Re: Query on postgres_fdw extension |
| Previous Message | David Fetter | 2021-05-31 16:41:05 | Re: Query is slow when order by and limit clause are used in the query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-06-01 10:24:31 | Re: Query on postgres_fdw extension |
| Previous Message | Tomas Pospisek | 2021-05-31 16:06:37 | Re: WAL accumulating, Logical Replication pg 13 |