Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid
Date
Msg-id 690349FD-8027-4054-B962-75F5F1E06463@yesql.se
Whole thread Raw
In response to Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid
List pgsql-hackers
> On 4 Aug 2025, at 17:18, Fujii Masao <masao.fujii@gmail.com> wrote:

I missed this thread while being on vacation, thanks for finding and fixing
this!

> This also got me thinking, if we simply define keywords as strings of
> non-whitespace characters, maybe we don't need to change the term "keyword"
> to "token" at all. I've updated the patch with that in mind. Thoughts?

Agreed, this should work fine, and it aligns the code somwhat with read_pattern
which is a good thing.

+ * in line buffer. Returns NULL when the buffer is empty or no keyword exists.
Since "is empty" could be interpreted as being a null pointer, maybe we should
add a if (!*line) check (or an Assert) before we dereference the passed in
buffer?

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: CREATE PUBLICATION with 'publish_generated_columns' parameter specified but unassigned
Next
From: vignesh C
Date:
Subject: Re: CREATE PUBLICATION with 'publish_generated_columns' parameter specified but unassigned