AlterTableCreateToastTable API still not right for pg_migrator - Mailing list pgsql-hackers

From Tom Lane
Subject AlterTableCreateToastTable API still not right for pg_migrator
Date
Msg-id 9564.1244748971@sss.pgh.pa.us
Whole thread Raw
Responses Re: AlterTableCreateToastTable API still not right for pg_migrator  (Bruce Momjian <bruce@momjian.us>)
Re: AlterTableCreateToastTable API still not right for pg_migrator  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
I just started reading the pg_migrator source code, and I notice that
we still didn't get AlterTableCreateToastTable's API right for
pg_migrator's usage.  It needs to be exposing an option to force
a particular OID for the toast table.  The way pg_migrator is handling
that now is both ugly and unsafe, and it's really pretty silly when the
underlying create_toast_table() function is perfectly capable of being
told what we want it to do.

There's still time to fix this before RC1.  I propose adding
"Oid toastOid" to AlterTableCreateToastTable's arguments, with
the semantics that if it's not InvalidOid then we attempt to create
the toast table with that OID.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Resolving 8.4 open items
Next
From: Tom Lane
Date:
Subject: Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?