Re: proposal: possibility to read dumped table's name from file
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Surafel Temesgen <surafel3000@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, vignesh C <vignesh21@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Daniel Gustafsson <daniel@yesql.se>
Date: 2020-11-11T05:49:43Z
Lists: pgsql-hackers
Hi Perhaps this feature could co-exist with a full blown configuration for >> pg_dump, but even then there's certainly issues with what's proposed- >> how would you handle explicitly asking for a table which is named >> " mytable" to be included or excluded? Or a table which has a newline >> in it? Using a standardized format which supports the full range of >> what we do in a table name, explicitly and clearly, would address these >> issues and also give us the flexibility to extend the options which >> could be used through the configuration file beyond just the filters in >> the future. >> > > This is the correct argument - I will check a possibility to use strange > names, but there is the same possibility and functionality like we allow > from the command line. So you can use double quoted names. I'll check it. > I checked echo "+t \"bad Name\"" | /usr/local/pgsql/master/bin/pg_dump --filter=/dev/stdin It is working without any problem Regards Pavel
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix array subscript warnings
- 17935e1fdf0a 17.0 landed
-
Read include/exclude commands for dump/restore from file
- a5cf808be55b 17.0 landed
-
Allow records to span multiple lines in pg_hba.conf and pg_ident.conf.
- 8f8154a503c7 14.0 cited