Re: Query related to pg_dump write to a pipe on a windows client and with compressed format

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Meera Nair <mnair(at)commvault(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Joel Howard <joelhoward(at)commvault(dot)com>
Subject: Re: Query related to pg_dump write to a pipe on a windows client and with compressed format
Date: 2023-12-01 18:19:28
Message-ID: 124574.1701454768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Meera Nair <mnair(at)commvault(dot)com> writes:
> We tried pg_dump write to a pipe with compressed format and faced issue as in thread referred here.
> It was on windows client and for postgres 9.2 version. So during pg_restore, seek error was seen.

Are you really using PG 9.2.something? If not, then what?

The problem here probably is that pg_restore is failing to detect
that the pipe input file is not seekable. We've had repeated rounds
of fixes to try to detect that reliably on Windows. I think it works
if you are running a current PG release (something shipped in the last
six months), but maybe not with older ones.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Owen Nelson 2023-12-01 19:08:49 Re: Understanding partial index selection
Previous Message Christophe Pettus 2023-12-01 17:50:49 Re: Help understand why DELETE is so slow