Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: "theshallow27(at)gmail(dot)com" <theshallow27(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
Date: 2026-10-02 03:25:05
Message-ID: CAKFQuwbjp=jg5_K3W3pP8cuO68B5R=NOuRRo6ZCvTMyZMyW8rQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thursday, October 1, 2026, shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> Do you mind sharing with us the use case of having a newline in
> a backup file?
>

The fix request seems like something we should just do barring foreseen
issues doing so. The system should not accept inputs it knows are
incompatible with the output it needs to produce. I agree there isn’t a
reason to try and make this usage actually work.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-10-02 03:49:27 Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
Previous Message Thiago Bonfante 2026-10-02 03:22:51 Backend crash (signal 11) in pg_trgm makesign() after ALTER TABLE ... SET STORAGE on a column with a gist_trgm_ops index