Re: why -Fdance archive format option works with ./pg_restore but not with ./pg_dump?

From: Srinath Reddy <srinath2133(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: why -Fdance archive format option works with ./pg_restore but not with ./pg_dump?
Date: 2025-01-24 08:04:19
Message-ID: CAFC+b6qKG5ogXTua1JmBZnZGk3Jm6287kLhuSv7pNEZZUM2YHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 24, 2025 at 1:42 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>
> `git blame` tells me that this switch statement goes back to 2001.
> Seeking a reason at this distance is unlikely to be productive. Probably
> we were not nearly as careful then as we are now about such things. Feel
> free to submit a patch tightening the test.
>

Hi Andrew,
thanks for the reply,here's the patch for the same.

Regards,
Srinath Reddy Sadipiralla
EnterpriseDB: http://www.enterprisedb.com

Attachment Content-Type Size
0001-Compare-whole-string-value-using-pg_strcasecmp-pg_restore.patch application/octet-stream 7.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2025-01-24 08:11:59 Re: XMLDocument (SQL/XML X030)
Previous Message Lukas Fittl 2025-01-24 07:44:01 Re: [PATCH] Optionally record Plan IDs to track plan changes for a query