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

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
Cc: Mark Wong <markwkm(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement
Date: 2025-11-07 14:47:36
Message-ID: CAB-JLwaDPJupWecAsvmNc7y7L5cQjV5P9epSFsTed1hEDbqUSA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em sex., 7 de nov. de 2025 às 11:27, Akshay Joshi <
akshay(dot)joshi(at)enterprisedb(dot)com> escreveu:

> I don’t think we need that statement. Could you please elaborate on where
> exactly it needs to be added?
>

well, these pg_get_..._ddl() functions will be cool for compare/clone
schemas in a multi tenant world.
Instead of dump/sed/restore a schema to create a new one, I could use
something like
select pg_get_table_ddl(oid) from pg_class where nspname = 'customer_050'
and relkind = 'r' union all
select pg_get_constraint_ddl(oid) from pg_constraint inner join pg_class on
... where ... union all
select pg_get_trigger_ddl(oid) from pg_trigger inner join pg_class on
... where ... union all
...

And pg_get_policy_ddl() will be part of these union all selects

Because that would be good to worry about create that only if it does not
exists or drop first too.

regards
Marcos

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2025-11-07 14:47:57 Re: Logical Replication of sequences
Previous Message Andres Freund 2025-11-07 14:41:05 Re: Xlogprefetcher: Use atomic add for increment counter