[BUGS] Postgres 9.1 and 9.2 crashing with exit code 9

[Tony Kurz]

Hello Guys

I have following situation:

PostgreSQL Database 9.1 32 Bit is crashing immediately, it's an Windows 2008R2.
I have patched to 9.2 64Bit, but is crashing with the same Exit code

What is "exit code 9"??
Here is an cut from the postgres.log

013-01-31 14:42:08 CETCONTEXT:  automatic vacuum of table 
"cloud.public.m201301_devicestatus"2013-01-31 14:43:14 CETLOG:  server process 
(PID 5820) exited with exit code 9
2013-01-31 14:43:14 CETLOG:  terminating any other active server processes
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.
2013-01-31 14:43:14 CETHINT:  In a moment you should be able to reconnect to 
the database and repeat your command.
2013-01-31 14:43:14 CETWARNING:  terminating connection because of crash of 
another server process
2013-01-31 14:43:14 CETDETAIL:  The postmaster has commanded this s

[BUGS] BUG #7868: Different class on numeric number through PgOleDb-1.0.0.20

[kensanmail]

The following bug has been logged on the website:

Bug reference:  7868
Logged by:  Ken Suzuki
Email address:  kensanm...@gmail.com
PostgreSQL version: 9.0.4
Operating system:   CentOS R-5.6
Description:

It's different class numeric number from DB through PgOleDb-1.0.0.20 when
the number is just n (ex20,000). I can see only "n" on my deliverable
(ex 2) from numeric(14,3) database. Is it knowns bug ? 



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #7869: Expressions in a view for rows that are not part of the view result set are still evaluated

[bernardjech]

The following bug has been logged on the website:

Bug reference:  7869
Logged by:  Bernard Jech
Email address:  bernardj...@yahoo.com
PostgreSQL version: 9.2.3
Operating system:   Mac OS X 10.6.8
Description:

-- Create the tables:

CREATE TABLE netblock (
  id INTEGER,
  ip_address inet NOT NULL
);

CREATE TABLE ipv4 (
  netblock_id integer
);

-- Insert data:

INSERT INTO netblock VALUES(1, '2605:ee00::/32');
INSERT INTO netblock VALUES(2, '68.67.181.7/26');
INSERT INTO ipv4 VALUES(2);

-- Create the view:

CREATE OR REPLACE VIEW subnet AS
SELECT ipv4.netblock_id AS id,
  set_masklen(n.ip_address, 32) - inet '0.0.0.0' AS cidr_address
FROM ipv4 JOIN netblock n ON ipv4.netblock_id = n.id;

If you select all rows from the view subnet, you get the expected result:

pokus=> select * from subnet;
 id | cidr_address 
+--
  2 |   1145287943
(1 row)

The surprising part comes when you add a WHERE clause to the SELECT
statement to select only this one row:

pokus=> select * from subnet where cidr_address = 1145287943;
ERROR:  cannot subtract inet values of different sizes

This is apparently caused by the IPv6 entry in the netblock table but this
row should be excluded by the inner JOIN in the VIEW definition.



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs