Re: Query on postgres_fdw extension - Mailing list pgsql-general

From Bharath Rupireddy
Subject Re: Query on postgres_fdw extension
Date
Msg-id CALj2ACXJOvjg1zhpB7RSC3jydFxEJumvDbfrG4fBHZuZFQKxNw@mail.gmail.com
Whole thread Raw
In response to Query on postgres_fdw extension  (Swathi P <swathi.bluepearl@gmail.com>)
Responses Re: Query on postgres_fdw extension  (Swathi P <swathi.bluepearl@gmail.com>)
List pgsql-general
On Tue, Jun 1, 2021 at 3:31 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
>
> Hi,
>
> On Fri, May 14, 2021 at 6:08 PM Swathi P <swathi.bluepearl@gmail.com> wrote:
> > In our sharding solution, we have multiple coodinator nodes. If we declare the table column as serial data type, we
mightend up having duplicate values for id column in the table_a in host_b (data node) as cconnections come from
multiplecoordinatoor 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.
Letme 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?

Perhaps, as a redundant node to avoid single point of failures? It's
just a guess as I'm not the right one to answer that question though.

With Regards,
Bharath Rupireddy.



pgsql-general by date:

Previous
From: Tomas Pospisek
Date:
Subject: Re: WAL accumulating, Logical Replication pg 13
Next
From: Zahir Lalani
Date:
Subject: RE: Framework for 0 downtime deploys