From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Srinath Reddy <srinath2133(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Non-text mode for pg_dumpall |
Date: | 2025-03-11 14:42:53 |
Message-ID: | 202503111442.yrr22bylsycg@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Mar-11, Mahendra Singh Thalor wrote:
> On Wed, 5 Mar 2025 at 20:42, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > Okay, we should probably fix that, but I think the new map.dat file your
> > patch adds is going to make the problem worse, because it doesn't look
> > like you handled that case in any particular way that would make it not
> > fail.
>
> As Jian also pointed out, we should not allow \n\r in dbnames. I am
> keeping dbanames as single line names only.
Ehm, did you get consensus on adding such a restriction?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Álvaro Herrera | 2025-03-11 14:46:52 | Re: bogus error message for ALTER TABLE ALTER CONSTRAINT |
Previous Message | Tom Lane | 2025-03-11 14:17:28 | Re: Statistics import and export: difference in statistics of materialized view dumped |