How about adding this patch to postgresql it will slove the problem? On Sun, Jul 5, 2009 at 8:10 PM, Greg Stark<gsst...@mit.edu> wrote: > On Sun, Jul 5, 2009 at 4:28 PM, Tom Lane<t...@sss.pgh.pa.us> wrote: >> when i done dump->restore i >>> have surprise, >>> Column ordering was changed. >> >> This is not a bug, it's the intended behavior. > > I thought that was a bug, just one that was too hard to fix for the > problems it caused. It might be more fixable if we get around to the > work that was discussed earlier where we separate attnum into three > different values. > > Oleg: note that having the columns in the same position allows some > optimizations in the executor so it's probably a good thing if it > hasn't broken your application. > > -- > greg > http://mit.edu/~gsstark/resume.pdf >
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
