Thank you everyone for responding.
Appreciate your help.
Looks like I need to understand the concepts a little more in detail , to
be able to ask the right questions, but atleast now I can look at the
relevant docs.
On Wed, 13 Mar 2019 at 2:44 PM Julien Rouhaud wrote:
> On Wed, Mar 13, 2019 a
On Wed, Mar 13, 2019 at 9:50 AM Laurenz Albe wrote:
>
> Vijaykumar Jain wrote:
> > I was asked this question in one of my demos, and it was interesting one.
> >
> > we update xmin for new inserts with the current txid.
> > now in a very high concurrent scenario where there are more than 2000
> > c
Vijaykumar Jain wrote:
> I was asked this question in one of my demos, and it was interesting one.
>
> we update xmin for new inserts with the current txid.
> now in a very high concurrent scenario where there are more than 2000
> concurrent users trying to insert new data,
> will updating xmin va
I may have misunderstood the documentation or your question, but I had
the understanding that xmin is not updated, but is only set on insert
(but yes, also for update, but updates are also inserts for Postgres as
updates are executed as delete/insert)
from https://www.postgresql.org/docs/10/ddl
On 3/12/19 1:02 PM, Vijaykumar Jain wrote:
no i mean not we end users, postgres does it (?) via the xmin and xmax
fields from inherited tables :) if that is what you wanted in a why
or are you asking, does postgres even update those rows and i am wrong
assuming it that way?
Not sure where the
no i mean not we end users, postgres does it (?) via the xmin and xmax
fields from inherited tables :) if that is what you wanted in a why
or are you asking, does postgres even update those rows and i am wrong
assuming it that way?
since the values need to be atomic,
consider the below analogy
as
On 3/12/19 12:19 PM, Vijaykumar Jain wrote:
I was asked this question in one of my demos, and it was interesting one.
we update xmin for new inserts with the current txid.
Why?
now in a very high concurrent scenario where there are more than 2000
concurrent users trying to insert new data,
w
I was asked this question in one of my demos, and it was interesting one.
we update xmin for new inserts with the current txid.
now in a very high concurrent scenario where there are more than 2000
concurrent users trying to insert new data,
will updating xmin value be a bottleneck?
i know we sho
