Re: Intermittent errors when fetching cursor rows on PostgreSQL 16

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Enrico Schenone <eschenone(at)cleistech(dot)it>, pgsql-general(at)lists(dot)postgresql(dot)org
Cc: Massimo Catti <mcatti(at)cleistech(dot)it>, Livio Pizzolo <lpizzolo(at)cleistech(dot)it>
Subject: Re: Intermittent errors when fetching cursor rows on PostgreSQL 16
Date: 2025-01-14 17:56:33
Message-ID: 9dab3561-3b45-4dac-9522-c84192f87d52@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/13/25 11:56 PM, Enrico Schenone wrote:
> Il 13/01/25 18:26, Adrian Klaver ha scritto:

>> In your OP you stated:
>>
>> "Production environments can be:
>>
>>  * Distinct application server and DB server on distinct subnets (no
>>     dropped packet detected on firewall, no memory/disk/network failure
>>     detected by "nmon" tool)
>>   * Distinct application server and DB server on same subnet (no
>> firewall)
>>   * Same server for PostgreSQL and applications
>> "
>>
>> In all those cases are the various servers all running completely
>> within the providers infrastructure?
>>
> No, the second production environment is On Premises at the customer
> Datacenter under the same vmware hypervisor.en

Which environment did you run the recent prolonged test against?

> I'll make more investigations on second and third environments by
> increasing the verbosity of both DB and Application logs.
>
> *Enrico Schenone*
> Software Architect
>

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Igor Korot 2025-01-14 18:42:41 Fwd: Lock in postgreSQL
Previous Message Tom Lane 2025-01-14 14:19:53 Re: Postgresql database terminates abruptly with too many open files error