Re: Query on Postgres SQL transaction

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: "Bandi, Venkataramana - Dell Team" <Venkataramana(dot)Bandi(at)dellteam(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "Kishore, Nanda - Dell Team" <Nanda(dot)Kishore(at)Dellteam(dot)com>, "Alampalli, Kishore" <Kishoreravishankar(dot)Alampalli(at)dellteam(dot)com>
Subject: Re: Query on Postgres SQL transaction
Date: 2024-03-27 16:01:34
Message-ID: 0927c6dc-2f64-4ca0-96e5-554ac1f14fed@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/27/24 04:29, Bandi, Venkataramana - Dell Team wrote:
> Hi,
>
> As l already mentioned, for this specific node also data is persisting but sometimes(randomly) data is not persisting.

How do you know which data is not persisting?

>
> As you mentioned our application doesn't have any restrictions on OS level and on network etc.
>
> different OS or OS version, different encoding, different location on the network, different data it is working, etc.

I don't understand what the above is saying. Do you mean there are
differences in these attributes between the nodes or no differences?

Also please do not top post, use either bottom or inline posting per:

https://en.wikipedia.org/wiki/Posting_style

>
> Regards,
> Venkat
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Ross 2024-03-27 16:02:11 Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function
Previous Message Ц 2024-03-27 15:56:52 Re: Active sessions does not terminated due to statement_timeout