Re: proposal: possibility to read dumped table's name from file
Julien Rouhaud <rjuju123@gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Andrew Dunstan <andrew@dunslane.net>, John Naylor <john.naylor@enterprisedb.com>, Erik Rijkers <er@xs4all.nl>, Justin Pryzby <pryzby@telsasoft.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, Tomas Vondra <tomas.vondra@enterprisedb.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: 2022-10-18T09:33:29Z
Lists: pgsql-hackers
On Thu, Oct 13, 2022 at 11:46:34AM -0700, Andres Freund wrote: > Hi, > > On 2022-10-07 07:26:08 +0200, Pavel Stehule wrote: > > I am sending version with handy written parser and meson support > > Given this is a new approach it seems inaccurate to have the CF entry marked > ready-for-committer. I've updated it to needs-review. I just had a quick look at the rest of the patch. For the parser, it seems that filter_get_pattern is reimplementing an identifier parsing function but isn't entirely correct. It can correctly parse quoted non-qualified identifiers and non-quoted qualified identifiers, but not quoted and qualified ones. For instance: $ echo 'include table nsp.tbl' | pg_dump --filter - >/dev/null $echo $? 0 $ echo 'include table "TBL"' | pg_dump --filter - >/dev/null $echo $? 0 $ echo 'include table "NSP"."TBL"' | pg_dump --filter - >/dev/null pg_dump: error: invalid format of filter on line 1: unexpected extra data after pattern This should also be covered in the regression tests. I'm wondering if psql's parse_identifier() could be exported and reused here rather than creating yet another version. Nitpicking: the comments needs some improvements: + /* + * Simple routines - just don't repeat same code + * + * Returns true, when filter's file is opened + */ + bool + filter_init(FilterStateData *fstate, const char *filename) also, is there any reason why this function doesn't call exit_nicely in case of error rather than letting each caller do it without any other cleanup? + /* + * Release allocated sources for filter + */ + void + filter_free_sources(FilterStateData *fstate) I'm assuming "ressources" not "sources"? + /* + * log_format_error - Emit error message + * + * This is mostly a convenience routine to avoid duplicating file closing code + * in multiple callsites. + */ + void + log_invalid_filter_format(FilterStateData *fstate, char *message) mismatch between comment and function name (same for filter_read_item) + static const char * + filter_object_type_name(FilterObjectType fot) No description. /* * Helper routine to reduce duplicated code */ void log_unsupported_filter_object_type(FilterStateData *fstate, const char *appname, FilterObjectType fot) Need more helpful comment.
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