On Tue, Nov 4, 2025 at 1:58 PM Jim Jones <[email protected]> wrote:
>
> Do you think that an overload in pg_proc.dat with oid as parameter would
> make sense here? e.g.
>
> { oid => '2322',
> descr => 'total disk space usage for the specified tablespace',
> proname => 'pg_tablespace_size', provolatile => 'v', prorettype =>
> 'int8',
> proargtypes => 'oid', prosrc => 'pg_tablespace_size_oid' },
> { oid => '2323',
> descr => 'total disk space usage for the specified tablespace',
> proname => 'pg_tablespace_size', provolatile => 'v', prorettype =>
> 'int8',
> proargtypes => 'name', prosrc => 'pg_tablespace_size_name' },
>
> Using name as parameter is more user friendly than OID.
Because users usually do not know the oids. Constructing
the DDL from the name appears better as it contains a name
in it. So, no gain in having an OID version of
pg_get_tablespace_ddl.
PFA, v3 patch set. It has some cosmetic changes and few
improvements in the new code added by Manni in v2. Also, the
new test case added did not have a DROP statement for the
tablespace created, which caused make-world failure. So, I
corrected that too.
Regards,
Nishant Sharma.
EDB, Pune.
v3-0001-Adds-pg_get_tablespace_ddl-function.patch
Description: Binary data
