Re: Non-text mode for pg_dumpall

From: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
To: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Cc: Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Non-text mode for pg_dumpall
Date: 2026-01-02 07:57:35
Message-ID: CAC6VRoa+7CxZ6kTYuxKH9A8H_MKkNEvjSaYv3QyiqJ=TpT0sfg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 12, 2025 at 9:47 PM Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
wrote:

>
> > [edb(at)1a1c15437e7c bin]$ ./psql postgres
> > psql (19devel)
> > Type "help" for help.
> > postgres=# \dt
> > Did not find any tables.
> > postgres=#
> >
> > regards,
> >
>
> Hi Tushar,
> This is the handling of command line arguments.
> In code, after "-f", we expect file name, but here you are using "-C"
> which will be considered as file name. This is the case for all the
> command line arguments.
>
> If pg_restore has the "-f" option, then the "-d database" name can't
> be given and data will be copied into "-f filename" (it will not be
> restored in the cluster).
>
> Please let me know if you still have some doubts.
>
> Thanks Mahendra , that was very helpful.

Please refer this scenario where i am getting error like:
"psql:output_script4.sql:95: error: backslash commands are restricted; only
\unrestrict is allowed"
if i run the .sql file generated by pg_restore command

Steps to reproduce:
./pg_dumpall -Ft -f dump.tar
./pg_restore -Ft dump.tar -C -v -f output_script.sql
run this .sql file against a new cluster ( \i output.script.sql)
restore will be done successfully but there are a few error like this
psql:output_script4.sql:95: error: backslash commands are restricted; only
\unrestrict is allowed

Is this expected?

regards,

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-01-02 08:05:17 Re: Non-text mode for pg_dumpall
Previous Message Babak Ghadiri 2026-01-02 07:55:07 Parallelizing startup with many databases