Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement

Philip Alger <paalger0@gmail.com>

From: Philip Alger <paalger0@gmail.com>

To: Akshay Joshi <akshay.joshi@enterprisedb.com>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-10-16T12:36:05Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Avoid leaking system path from pg_available_extensions
- db5ed03217b9 19 (unreleased) cited
postgres_fdw, dblink: Validate use_scram_passthrough values
- 8a86aa313a71 19 (unreleased) cited
Make pg_get_expr() more bulletproof.
- 6867f963e319 15.0 cited

Hi Akshay,


>>> As for the statement terminator, it’s useful to include it, while
>> running multiple queries together could result in a syntax error. In my
>> opinion, there’s no harm in providing the statement terminator.
>>
> However, I’ve modified the logic to add the statement terminator at the
> end instead of appending to a new line.
>
>>
>>
Regarding putting the terminator at the end, I think my original comment
got cut off by my poor editing. Yes, that's what I was referring to; no
need to append it to a new line.

-- 
Best, Phil Alger