RE: An I/O error occurred while sending to the backend (PG 13.4)

>From: Ranier Vilela >Sent: Thursday, February 24, 2022 08:46 >To: Justin Pryzby >Cc: l...@laurent-hasson.com; pgsql-performa...@postgresql.org >Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > >Em qui., 24 de fev. de 2022 às 09:59, Justin Pryzby >

RE: An I/O error occurred while sending to the backend (PG 13.4)

> -Original Message- > From: Justin Pryzby > Sent: Friday, February 25, 2022 08:02 > To: l...@laurent-hasson.com > Cc: pgsql-performa...@postgresql.org > Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > > On Wed, Feb 23, 2022 at

Re: An I/O error occurred while sending to the backend (PG 13.4)

On Mon, Feb 28, 2022 at 09:43:09PM +, l...@laurent-hasson.com wrote: >On Wed, Feb 23, 2022 at 07:04:15PM -0600, Justin Pryzby wrote: >> > And the aforementioned network trace. You could set a capture filter > on TCP >> > SYN|RST so it's not absurdly large. From my notes, it mig

Re: Never Ending query in PostgreSQL

On 2/26/22 23:40, Kumar, Mukesh wrote: Hi Team, Can you please help in tunning the attached query as , i am trying to run this query and it runs for several hours and it did not give any output. I am not able to generate the explain analyze plan as well and it keeps on running for several h

Re: Never Ending query in PostgreSQL

On 2/27/22 12:20, Jeff Janes wrote: Several hours is not all that long. Well, the pyramids in the Valley of the Kings last for around 4500 years. Dinosaurs have ruled the Earth for approximately 120 million years. Solar system is 5 billion years old. Cosmos is around 13 billion years old. Co

Re: Advice needed: query performance deteriorates by 2000% within 1 minute

Hello, Michael, Tom: thanks for all the insights and informations in your previous mails. A quick update of the explain outputs (this time using explain (analyze, buffers, verbose)) *The good: * *LOG Time: | 2022-02-28 09:30:01.400777+01 | order rows: | 9668* Limit (cost=616.37..653.30 ro