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: Daniel Gustafsson <daniel@yesql.se>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>,
Justin Pryzby <pryzby@telsasoft.com>, Dean Rasheed <dean.a.rasheed@gmail.com>, Stephen Frost <sfrost@snowman.net>, Surafel Temesgen <surafel3000@gmail.com>, vignesh C <vignesh21@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-10-01T16:00:17Z
Lists: pgsql-hackers
pá 1. 10. 2021 v 15:19 odesílatel Daniel Gustafsson <daniel@yesql.se> napsal: > I took another pass over this today and touched up the documentation (docs > and > code) as well as tweaked the code a bit here and there to both make it fit > the > pg_dump style better and to clean up a few small things. I've also added > a set > of additional tests to cover more of the functionality. > > I'm still not happy with the docs, I need to take another look there and > see if > I make them more readable but otherwise I don't think there are any open > issues > with this. > > As has been discussed upthread, this format strikes a compromise wrt > simplicity > and doesn't preclude adding a more structured config file in the future > should > we want that. I think this takes care of most comments and opinions made > in > this thread. > It looks well. Thank you Pavel > -- > Daniel Gustafsson https://vmware.com/ > >
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