[BUGS] hstore: null value is treated as empty string by avals function

hstore: null value is treated as empty string by avals function # select avals('gfds'=>null) = array[null], avals('gfds'=>null) = array[''], version(); ?column? | ?column? | version --+--+-

[BUGS] BUG #4887: inclusion operator (@>) on tsqeries behaves not conforming to documentation

The following bug has been logged online: Bug reference: 4887 Logged by: Alexey Bashtanov Email address: bashta...@imap.cc PostgreSQL version: 8.3.1, 8.3.7 Operating system: Linux 2.6.20 FC5 i686, Linux 2.6.27 FC10 i686 Description:inclusion operator (@>) on tsqer

[BUGS] BUG #4513: VACUUM FULL fails with "out of memory" error

The following bug has been logged online: Bug reference: 4513 Logged by: Alexey Bashtanov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.1 Operating system: Red Hat Linux 2.6.20-1.2320.fc5smp i686 Description:VACUUM FULL fails with "out of memory&q

Re: [BUGS] BUG #4271: dropped columns conflict with returning rules

Hello, Tom! > What did you do *exactly*? Here's the example of command sequence that lead to this error: luh=# create table foo(a int); CREATE TABLE luh=# alter TABLE foo add column b int; ALTER TABLE luh=# alter TABLE foo drop column b; ALTER TABLE luh=# alter TABLE foo add column c int; ALT

[BUGS] BUG #4271: dropped columns conflict with returning rules

The following bug has been logged online: Bug reference: 4271 Logged by: Alexey Bashtanov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.1 Operating system: linux Description:dropped columns conflict with returning rules Details: I have created a