think
anyone would want to add dropped columns to any result sets.
it's the automatic rowtype of the table that is wrong,
because it has not been updated (and apparently needs to be)
to reflect the current state of the table.
i hope this does get fixed or dropping columns is a big mistak
m srf()" all the time
(it works better for multi-column sets anyway).
does this mean that "select srf()" is no longer deprecated?
cheers,
raf
> 2009/2/10 Daniel Migowski :
> > Hello dear PostgreSQL developers,
> >
> > I noticed the following strange behavi
The following bug has been logged online:
Bug reference: 6158
Logged by: raf
Email address: r...@raf.org
PostgreSQL version: 9.0.4
Operating system: n/a
Description:documentation error (grammar/typo)
Details:
in the documentation available at:
http
The following bug has been logged online:
Bug reference: 6165
Logged by: raf
Email address: r...@raf.org
PostgreSQL version: 9.0.4
Operating system: N/A
Description:documentation bug in plpgsql-declarations.html and
plpgsql-statements.html (or plpgsql parser bug
hi,
i've just upgraded to 9.1.4 on macosx-10.6.8 and psql crashes
whenever the -h option is used (either with "localhost" or any
other hostname). i only have hostssl connections.
attached is a macosx crash report in case it helps.
i think i'll downgrade now :-)
Tom Lane wrote:
> raf writes:
> > i've just upgraded to 9.1.4 on macosx-10.6.8 and psql crashes
> > whenever the -h option is used (either with "localhost" or any
> > other hostname). i only have hostssl connections.
>
> > attached is a macosx
