On 2/21/07, Gregory Stark <[EMAIL PROTECTED]> wrote:
So yes, there would be a use case for specifying the physical column layout when pg_migrator is doing the pg_dump/restore. But pg_migrator could probably just update the physical column numbers itself. It's not like updating system catalog tables directly is any more of an abstraction violation than swapping files out from under the database...
If people are ok with that answer, then I'll gladly stop suggesting that ALTER TABLE be able to explicitly set storage positions. I was just trying to avoid forcing a tool like pg_migrator to muck with the system catalogs. phil ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
