On Sat, Sep 30, 2023 at 03:55:20PM +1000, James Healy wrote:
> It did make me curious though: would it be possible for postgres to
> support gradual migration from integer to bigint in a more
> transparent way, where new and updated tuples are written as bigint,
> but existing tuples can be read as integer?
Language police: this is the *opposite* of "transparent". "trasparent"
and "automated" are not synonyms.
--
Ian