Re: [BUGS] BUG #5389: Column order on dump/reload broken from defined setof function

2010-03-28 Thread Robert Haas
On Fri, Mar 26, 2010 at 7:00 AM, Dimitri Fontaine wrote: > "Timothy Seever" writes: >> CREATE FUNCTION testfunc() RETURNS setof tablec AS $BODY$ SELECT * FROM >> tablec; $BODY$ LANGUAGE 'sql' STABLE; > > Common wisdom saith to never ever use "SELECT *" in your code. You just > found out a reason

Re: [BUGS] BUG #5389: Column order on dump/reload broken from defined setof function

2010-03-26 Thread Dimitri Fontaine
"Timothy Seever" writes: > CREATE FUNCTION testfunc() RETURNS setof tablec AS $BODY$ SELECT * FROM > tablec; $BODY$ LANGUAGE 'sql' STABLE; Common wisdom saith to never ever use "SELECT *" in your code. You just found out a reason why. Regards, -- dim -- Sent via pgsql-bugs mailing list (pgsql

Re: [BUGS] BUG #5389: Column order on dump/reload broken from defined setof function

2010-03-25 Thread Tom Lane
"Timothy Seever" writes: > Adding a column to an inherited table in-place works as expected with the > combined table/etc. However on dump/reload the physical order changes, so > any? predefined select from a setof function pulling from the combined table > will result in a mismatch. Yup. This

[BUGS] BUG #5389: Column order on dump/reload broken from defined setof function

2010-03-25 Thread Timothy Seever
The following bug has been logged online: Bug reference: 5389 Logged by: Timothy Seever Email address: tim.see...@gmail.com PostgreSQL version: 8.3.5, others Operating system: Linux Description:Column order on dump/reload broken from defined setof function Details: