vjegatha88 | 9 Nov 12:09 2013
Picon

BUG #8584: Cross Tab Queries

The following bug has been logged on the website:

Bug reference:      8584
Logged by:          jvjv
Email address:      vjegatha88 <at> gmail.com
PostgreSQL version: 9.3.1
Operating system:   Win 8
Description:        

How to work with crosstab2 function , i hav 2 set of category for qty &
value in monthly analysis..

--

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

rathodsa | 9 Nov 20:30 2013
Picon

BUG #8585: 32 bit ODBC driver is not working with Excel 2010 w/PowerPivot

The following bug has been logged on the website:

Bug reference:      8585
Logged by:          Aashish Rathod
Email address:      rathodsa <at> gmail.com
PostgreSQL version: 9.3.1
Operating system:   Windows 7 Prof 64 bit SP1
Description:        

i am using the 32 bit driver with Excel 2010 32 bit version.

i am going through the PowerPivot wizard.
When i "Select from a list of tables and views to choose the data to
import.", no tables/views appear. the message is that no tables were found
in the data source. Check the connection information and login credentials.

When i select "write a query that will specify the data to import", then you
cannot type 'select * from fact_revenue'.
you have to type each field in the list.

--

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

evgeniy.skomorokhov | 7 Nov 08:35 2013
Picon

BUG #8582: field serial getted incorrect value from automaticaly created its sequence

The following bug has been logged on the website:

Bug reference:      8582
Logged by:          Evgeniy Skomorokhov
Email address:      evgeniy.skomorokhov <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   ubuntu precise 12.04
Description:        

Automaticaly created sequence takes values ​​from the range [1;
9223372036854775807] but max value of field which will be filled from
sequence - max of type integer (2147483647).

In PostgreSQL we can set field type "serial" during creting table like:
CREATE TABLE test1(
id serial
);

Then we get table and sequence structure like 
/*
NOTICE:  CREATE TABLE will create implicit sequence "test1_id_seq" for
serial column "test1.id"

-- Created structures test1 and test1_id_seq:

CREATE TABLE test1
(
  id serial NOT NULL
)
WITH (
(Continue reading)

peeyush.singla | 7 Nov 08:19 2013
Picon

BUG #8581: PG::UndefinedObject: ERROR: type "json" does not exist

The following bug has been logged on the website:

Bug reference:      8581
Logged by:          peeyush singla
Email address:      peeyush.singla <at> gmail.com
PostgreSQL version: 9.3.1
Operating system:   ubuntu 13.10
Description:        

I am using pg with rails application my version of pg is 9.3.1 i cloned this
project from someone but whenever I am trying to run rake db:migrate it is
giving me the error:- PG::UndefinedObject: ERROR:  type "json" does not
exist
I am using json in one column in migration:- e.g:-  add_column :filters,
:search_string, :json same application is working fine on 9.2.4 on mac but
when I am trying to do this on my system it's not working. I think here is
some issue wiht 9.3.1 with json support

--

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

gladchenkoigor | 7 Nov 12:30 2013
Picon

BUG #8583: I can't install this product

The following bug has been logged on the website:

Bug reference:      8583
Logged by:          Igor Gladchenko
Email address:      gladchenkoigor <at> hotmail.com
PostgreSQL version: 9.3.1
Operating system:   Windows XP SP3
Description:        

 can't install this product. When I run setup I get the following message: 
"There has been an error. 
Unable to write inside the TEMP environment variable path". 
I have the following environment variables: Temp=C:\Temp 
Tmp=C:\Tmp. 
What to do?

--

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

Rajagopal C.R | 6 Nov 13:59 2013
Picon

Please send me the steps to install Debugger-Plugin for Postgresql-9.2

Hi,
I am using  Postgresql-9.2 from last few months. Its a good DB server. 
I am trying to debug for procedures/functions. could you please send me the steps to install  Debugger-Plugin.

--

Rajagopal CR 

| Mobile: 8892096843
rajagopalcr7 <at> gmail.com


Follow me on 

suri | 6 Nov 08:22 2013
Picon

(unknown)





I have created a function to update the data in the table in postgres and i have 33k records to update. When i was calling the function as SQL the data is updated fine. But when i was calling the same function through callable statement only about 28k records are updated in the table and it was skipping the remaining records no exceptions have thrown. please help me on this issue.

this is my code. CallableStatement callStatement = ConnectionDB.getConnectionInstance().prepareCall(" { ? = call functionname()}"); callStatement.registerOutParameter(1, Types.VARCHAR); callStatement.execute();




/*- – - – - – – - – – - – – - – – - – – - – – - – – - – – - – – - – – - -

Please consider your environmental responsibility.
Before printing this e-mail message, ask yourself whether you really need a hard copy.

Life is what happens to you, while you're busy making other plans

We do not inherit the earth from our ancestors; we borrow it from our children. 
Leave them a living planet reduce your carbon foot print.
--------------------------------------------------------------------------------------------*/ 






yours suri chinna
bashtanov | 6 Nov 11:42 2013

BUG #8580: search_path unexpected behavior with pg_temp

The following bug has been logged on the website:

Bug reference:      8580
Logged by:          Alexey Bashtanov
Email address:      bashtanov <at> imap.cc
PostgreSQL version: 9.2.4
Operating system:   Linux Centos 6.4
Description:        

[STEPS TO REPRODUCE]
CREATE OR REPLACE FUNCTION foo() RETURNS void 
AS $$
begin
  create temporary table zoo () on commit preserve rows;
  delete from zoo;
  drop table zoo;
end;
$$ language plpgsql set search_path = pg_catalog, public, pg_temp;

begin;
select foo();
abort;
begin;
select foo();

[EXPECTED]
no errors
[RECEIVED]
ERROR:  relation "zoo" does not exist
LINE 1: delete from zoo

[ALSO]
1)reproducibility between 50% and 100%
2)also can be reproduced on pg 9.1.9
3)reproduced if replace delete by perform
4)not reproduced if replace delete by alter

Regards, 
  Alexey Bashtanov

--

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

rgr | 6 Nov 09:54 2013
Picon

BUG #8579: CoreDump of background writer process

The following bug has been logged on the website:

Bug reference:      8579
Logged by:          Rene Gruen
Email address:      rgr <at> cslab.de
PostgreSQL version: 9.0.13
Operating system:   QNX 6.5
Description:        

Greetings everybody.

We are using postgresql for round about 10 years in our software. Starting
with our update from version 8.3 to 9.0 we are receveing coredumps of the
server process.
This seems to happen while inserting different data into different tables
via COPY.
I do not add some example data / table-descriptions, because the error does
not ocure each time (also using the same data and the same table)

I have seen the core using ecpg (examples one and two) and using psql
(example 3).
Each time there is a message like "could not seek to block XXX in file YYY"
just before the server terminates.

We are using QNX 6.5 SP 1 and a port based on the pkgsrc.

I hope the attached data will help to locate the problem.

Example one (using a "normal" version):

Logfile:
---633794700-2013-11-01 00:09:58 CET:CONTEXT:  automatic analyze of table
"gltdb.glttab001.glt_dp_para_trend_1hour"
---1507368-2013-11-01 00:10:23 CET:LOG:  received SIGHUP, reloading
configuration files
---1519657-2013-11-01 00:10:23 CET:ERROR:  could not seek to block 149256 in
file "pg_tblspc/17639/PG_9.0_201008051/16387/28109.1": Interrupted function
call
---1519657-2013-11-01 00:10:23 CET:CONTEXT:  writing block 149256 of
relation pg_tblspc/17639/PG_9.0_201008051/16387/28109
---1507368-2013-11-01 00:11:58 CET:LOG:  background writer process (PID
1519657) was terminated by signal 11: segmentation violation
---1507368-2013-11-01 00:11:58 CET:LOG:  terminating any other active server
processes

contents of the dump-file:

#0  0x00000000 in ?? ()
#1  0x08205ef4 in BackgroundWriterMain ()
#2  0x080e2759 in AuxiliaryProcessMain ()
#3  0x0820bb87 in StartChildProcess ()
#4  0x0820deca in reaper ()
#5  <signal handler called>
#6  0xb033e412 in SignalWaitinfo () from /lib/libc.so.3
#7  0xb0371ef2 in _poll () from /lib/libc.so.3
#8  0xb0372253 in select () from /lib/libc.so.3
#9  0x0820f46b in PostmasterMain ()
#10 0x081b6bfb in main ()

Example two (using a debug-version):

Logfile:
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:31:46 CET:LOG: 
duration: 65108.037 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000002'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:33:21 CET:LOG: 
duration: 94909.477 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000003'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:35:24 CET:LOG: 
duration: 122674.228 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000004'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:37:44 CET:LOG: 
duration: 140464.505 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000005'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:40:06 CET:LOG: 
duration: 141908.285 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000006'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:42:34 CET:LOG: 
duration: 147574.417 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000007'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:44:46 CET:LOG: 
duration: 131793.832 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000008'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:48:08 CET:LOG: 
duration: 202173.063 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000009'
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:51:25 CET:LOG: 
duration: 196979.858 ms  execute copy_stmt: COPY glt_dp_para_trend_1min FROM
'/tmp/odbc5689466-65732-1-000010'
---1478697-2013-11-05 16:53:23 CET:ERROR:  could not seek to block 267907 in
file "pg_tblspc/17639/PG_9.0_201008051/16387/28106.2": Interrupted function
call
---1478697-2013-11-05 16:53:23 CET:CONTEXT:  writing block 267907 of
relation pg_tblspc/17639/PG_9.0_201008051/16387/28106
---1466408-2013-11-05 16:54:52 CET:LOG:  background writer process (PID
1478697) was terminated by signal 11: segmentation violation
---1466408-2013-11-05 16:54:52 CET:LOG:  terminating any other active server
processes
---1184063623-2013-11-05 16:54:52 CET:WARNING:  terminating connection
because of crash of another server process
---1184063623-2013-11-05 16:54:52 CET:DETAIL:  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.
---1184063623-2013-11-05 16:54:52 CET:HINT:  In a moment you should be able
to reconnect to the database and repeat your command.
GLTlogger[2777125]-gltdb-[local]-2908210-2013-11-05 16:54:52 CET:WARNING: 
terminating connection because of crash of another server process
GLTlogger[2777125]-gltdb-[local]-2908210-2013-11-05 16:54:52 CET:DETAIL: 
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.
GLTlogger[2777125]-gltdb-[local]-2908210-2013-11-05 16:54:52 CET:HINT:  In a
moment you should be able to reconnect to the database and repeat your
command.
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:54:52 CET:WARNING: 
terminating connection because of crash of another server process
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:54:52 CET:DETAIL:  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.
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:54:52 CET:HINT:  In a
moment you should be able to reconnect to the database and repeat your
command.
ODBChist[5689466]-gltdb-[local]-9003121-2013-11-05 16:54:52 CET:CONTEXT: 
COPY glt_dp_para_trend_1min, line 117201: "65732	2012-12-19
13:45:00+01	23016900.005000	1	I"
---1466408-2013-11-05 16:54:53 CET:LOG:  all server processes terminated;
reinitializing
---1752227881-2013-11-05 16:54:53 CET:LOG:  database system was interrupted;
last known up at 2013-11-05 16:52:06 CET
---1752227881-2013-11-05 16:54:53 CET:LOG:  database system was not properly
shut down; automatic recovery in progress
---1752227881-2013-11-05 16:54:53 CET:LOG:  redo starts at 38/D300E054
[unknown]-gltdb-[local]-1752231980-2013-11-05 16:55:00 CET:FATAL:  the
database system is in recovery mode
---1752227881-2013-11-05 16:55:10 CET:LOG:  invalid magic number 0000 in log
file 56, segment 221, offset 11935744
---1752227881-2013-11-05 16:55:10 CET:LOG:  redo done at 38/DDB60ED4
---1752227881-2013-11-05 16:55:10 CET:LOG:  last completed transaction was
at log time 2013-11-05 16:53:27.692009+01
---1752391757-2013-11-05 16:55:13 CET:LOG:  autovacuum launcher started
---1466408-2013-11-05 16:55:13 CET:LOG:  database system is ready to accept
connections

coredump:

Program terminated with signal 11, Segmentation fault.
[New pid 1478697 tid 1]
#0  0x00000000 in ?? ()

(gdb) bt
#0  0x00000000 in ?? ()
#1  0x08205ef4 in BackgroundWriterMain () at bgwriter.c:329
#2  0x080e2759 in AuxiliaryProcessMain (argc=2, argv=0x8047460) at
bootstrap.c:417
#3  0x0820bb87 in StartChildProcess (type=<value optimized out>) at
postmaster.c:4458
#4  0x0820deca in reaper (postgres_signal_arg=18) at postmaster.c:2418
#5  <signal handler called>
#6  0xb033e412 in SignalWaitinfo () from /lib/libc.so.3
#7  0xb0371ef2 in _poll () from /lib/libc.so.3
#8  0xb0372253 in select () from /lib/libc.so.3
#9  0x0820f46b in PostmasterMain (argc=8, argv=0x84b5100) at
postmaster.c:1414
#10 0x081b6bfb in main (argc=8, argv=0x84b5100) at main.c:188

(gdb) up
#1  0x08205ef4 in BackgroundWriterMain () at bgwriter.c:329
329     bgwriter.c: No such file or directory.
        in bgwriter.c

329 <at> bgwriter.c: MemoryContextResetAndDeleteChildren(bgwriter_context);

(gdb) print bgwriter_context
$1 = (MemoryContext) 0x84c0c00

(gdb) print *bgwriter_context
$3 = {type = T_Invalid, methods = 0x84c0d00, parent = 0x10, firstchild =
0x0, nextchild = 0x0, name = 0x0}
(gdb)

Example Tree (debug version):

psql-gltdb-[local]-29880389-2013-11-05 22:27:39 CET:LOG:  duration:
244502.586 ms  statement: COPY glttab018.pdbt_d4_contobject FROM STDIN;
psql-gltdb-[local]-30502981-2013-11-05 22:32:14 CET:LOG:  duration:
274090.058 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-31166533-2013-11-05 22:36:52 CET:LOG:  duration:
276984.615 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-31858757-2013-11-05 22:41:40 CET:LOG:  duration:
288205.898 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-32526405-2013-11-05 22:46:31 CET:LOG:  duration:
290317.574 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-33275974-2013-11-05 22:51:23 CET:LOG:  duration:
291812.346 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-33972293-2013-11-05 22:56:12 CET:LOG:  duration:
288272.888 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-34664517-2013-11-05 23:01:19 CET:LOG:  duration:
306371.118 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-35409990-2013-11-05 23:06:18 CET:LOG:  duration:
298632.302 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-36130886-2013-11-05 23:11:18 CET:LOG:  duration:
298665.298 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-36851782-2013-11-05 23:16:22 CET:LOG:  duration:
304064.471 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-37576773-2013-11-05 23:21:38 CET:LOG:  duration:
315617.703 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-38326341-2013-11-05 23:26:54 CET:LOG:  duration:
315162.772 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-39100485-2013-11-05 23:32:13 CET:LOG:  duration:
317958.345 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-39850053-2013-11-05 23:37:45 CET:LOG:  duration:
331930.207 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-40628293-2013-11-05 23:43:03 CET:LOG:  duration:
317776.373 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
psql-gltdb-[local]-41427014-2013-11-05 23:48:48 CET:LOG:  duration:
343849.383 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
---1634347-2013-11-05 23:50:58 CET:ERROR:  could not seek to block 13243 in
file "pg_tblspc/78600/PG_9.0_201008051/16387/79270": Interrupted function
call
---1634347-2013-11-05 23:50:58 CET:CONTEXT:  writing block 13243 of relation
pg_tblspc/78600/PG_9.0_201008051/16387/79270
psql-gltdb-[local]-42233926-2013-11-05 23:57:52 CET:LOG:  duration:
544057.747 ms  statement: COPY glttab018.pdbt_d4_contparameter FROM STDIN;
---1613866-2013-11-05 23:59:21 CET:LOG:  background writer process (PID
1634347) was terminated by signal 11: segmentation violation
---1613866-2013-11-05 23:59:21 CET:LOG:  terminating any other active server
processes
psql-gltdb-[local]-43360325-2013-11-05 23:59:21 CET:WARNING:  terminating
connection because of crash of another server process
psql-gltdb-[local]-43360325-2013-11-05 23:59:21 CET:DETAIL:  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.
psql-gltdb-[local]-43360325-2013-11-05 23:59:21 CET:HINT:  In a moment you
should be able to reconnect to the database and repeat your command.
psql-gltdb-[local]-43360325-2013-11-05 23:59:21 CET:CONTEXT:  COPY
pdbt_d4_contparameter, line 82696:
"919360	14666	2	0	1	1	0	0	0	Kühlzeit	0	0	0	I	10001	5224	0	-1"
---1613866-2013-11-05 23:59:23 CET:LOG:  all server processes terminated;
reinitializing
[unknown]-gltdb-[local]-43606062-2013-11-05 23:59:24 CET:FATAL:  the
database system is in recovery mode
---43606059-2013-11-05 23:59:24 CET:LOG:  database system was interrupted;
last known up at 2013-11-05 23:50:10 CET
---1613866-2013-11-05 23:59:24 CET:LOG:  received SIGHUP, reloading
configuration files
---43606059-2013-11-05 23:59:25 CET:LOG:  could not remove cache file
"base/849886/pg_internal.init": Interrupted function call
---43606059-2013-11-05 23:59:26 CET:LOG:  database system was not properly
shut down; automatic recovery in progress
---43606059-2013-11-05 23:59:26 CET:LOG:  redo starts at 14/B300F554
---1613866-2013-11-05 23:59:27 CET:LOG:  received SIGHUP, reloading
configuration files
---1613866-2013-11-05 23:59:27 CET:LOG:  parameter "autovacuum" changed to
"on"
[unknown]-gltdb-[local]-43773970-2013-11-05 23:59:32 CET:FATAL:  the
database system is in recovery mode
[unknown]-gltdb-[local]-43810834-2013-11-05 23:59:33 CET:FATAL:  the
database system is in recovery mode
[unknown]-gltdb-[local]-44539922-2013-11-06 00:04:35 CET:FATAL:  the
database system is in recovery mode
---43606059-2013-11-06 00:07:24 CET:LOG:  could not open file
"pg_xlog/0000000100000014000000C1" (log file 20, segment 193): No such file
or directory
---43606059-2013-11-06 00:07:24 CET:LOG:  redo done at 14/C0FFFFB0
---43606059-2013-11-06 00:07:24 CET:LOG:  last completed transaction was at
log time 2013-11-05 23:57:52.607898+01
---44941357-2013-11-06 00:07:29 CET:LOG:  autovacuum launcher started
---1613866-2013-11-06 00:07:29 CET:LOG:  database system is ready to accept
connections
---1613866-2013-11-06 00:13:02 CET:LOG:  received SIGHUP, reloading
configuration files
vacuumdb-gltdb-[local]-45871174-2013-11-06 01:14:08 CET:WARNING:  relation
"pdbt_d4_contparameter" page 21075 is uninitialized --- fixing
vacuumdb-gltdb-[local]-45871174-2013-11-06 01:14:08 CET:WARNING:  relation
"pdbt_d4_contparameter" page 21076 is uninitialized --- fixing
vacuumdb-gltdb-[local]-45871174-2013-11-06 01:14:08 CET:WARNING:  relation
"pdbt_d4_contparameter" page 21077 is uninitialized --- fixing
vacuumdb-gltdb-[local]-45871174-2013-11-06 01:18:02 CET:LOG:  duration:
3896493.745 ms  statement: VACUUM (ANALYZE);

contents of the core file:

Program terminated with signal 11, Segmentation fault.
[New pid 1634347 tid 1]
#0  0x00000000 in ?? ()

(gdb) bt
#0  0x00000000 in ?? ()
#1  0x08205ef4 in BackgroundWriterMain () at bgwriter.c:329
#2  0x080e2759 in AuxiliaryProcessMain (argc=2, argv=0x8047460) at
bootstrap.c:417
#3  0x0820bb87 in StartChildProcess (type=<value optimized out>) at
postmaster.c:4458
#4  0x0820deca in reaper (postgres_signal_arg=18) at postmaster.c:2418
#5  <signal handler called>
#6  0xb033e412 in SignalWaitinfo () from /lib/libc.so.3
#7  0xb0371ef2 in _poll () from /lib/libc.so.3
#8  0xb0372253 in select () from /lib/libc.so.3
#9  0x0820f46b in PostmasterMain (argc=8, argv=0x84b5100) at
postmaster.c:1414
#10 0x081b6bfb in main (argc=8, argv=0x84b5100) at main.c:188

(gdb) up
#1  0x08205ef4 in BackgroundWriterMain () at bgwriter.c:329
329     bgwriter.c: No such file or directory.
        in bgwriter.c

(gdb) print *bgwriter_context
$1 = {type = T_Invalid, methods = 0x84c0d00, parent = 0x10, firstchild =
0x0, nextchild = 0x0, name = 0x0}

--

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

robert | 6 Nov 02:07 2013

BUG #8578: loading a 33G (compressed) pg_dump into a fresh host and db instance crashes a postgresql process

The following bug has been logged on the website:

Bug reference:      8578
Logged by:          Robert Nix
Email address:      robert <at> urban4m.com
PostgreSQL version: 9.3.1
Operating system:   Linux Ubuntu 12.10
Description:        

Below are the logs revealing the failure:

2013-11-05 17:04:21 EST LOG:  server process (PID 5869) was terminated by
signal 9: Killed
2013-11-05 17:04:21 EST DETAIL:  Failed process was running: autovacuum:
ANALYZE data_partitions.zone_municipality_demog_houston
2013-11-05 17:04:21 EST LOG:  terminating any other active server processes
2013-11-05 17:04:21 EST WARNING:  terminating connection because of crash of
another server process
2013-11-05 17:04:21 EST DETAIL:  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-11-05 17:04:21 EST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2013-11-05 17:04:21 EST WARNING:  terminating connection because of crash of
another server process
2013-11-05 17:04:21 EST DETAIL:  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-11-05 17:04:21 EST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2013-11-05 17:04:21 EST WARNING:  terminating connection because of crash of
another server process
2013-11-05 17:04:21 EST DETAIL:  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-11-05 17:04:21 EST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2013-11-05 17:04:21 EST WARNING:  terminating connection because of crash of
another server process
2013-11-05 17:04:21 EST DETAIL:  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-11-05 17:04:21 EST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2013-11-05 17:04:21 EST CONTEXT:  COPY zone_zipcode_demog_orlando, line
8986
2013-11-05 17:04:23 EST LOG:  all server processes terminated;
reinitializing
2013-11-05 17:04:23 EST LOG:  database system was interrupted; last known up
at 2013-11-05 17:01:22 EST
2013-11-05 17:04:23 EST LOG:  database system was not properly shut down;
automatic recovery in progress
2013-11-05 17:04:23 EST LOG:  redo starts at 57/643FA1F8
2013-11-05 17:04:47 EST LOG:  unexpected pageaddr 56/E5784000 in log segment
00000001000000570000008F, offset 7880704
2013-11-05 17:04:47 EST LOG:  redo done at 57/8F783B68
2013-11-05 17:04:47 EST LOG:  last completed transaction was at log time
2013-11-05 17:01:52.611585-05
2013-11-05 17:04:53 EST LOG:  database system is ready to accept
connections
2013-11-05 17:04:53 EST LOG:  autovacuum launcher started

psql reports:

WARNING:  terminating connection because of crash of another server process
DETAIL:  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.
HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
CONTEXT:  COPY zone_zipcode_demog_orlando, line 8986
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
connection to server was lost

The command being issued is:

dropdb u; createdb u; cat u.sql.gz | gzip -d | psql u

u.sql.gz was created as:

pg_dump u | gzip >u.sql.gz

The database from which the dump was created is the same, 9.3.1, same
operating system, both Ubuntu 12.10. Db's have same extensions installed.
The source database shows no signs of issues.

--

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

dominik | 5 Nov 21:53 2013

BUG #8577: pg_dump custom format exported dump can't be imported again

The following bug has been logged on the website:

Bug reference:      8577
Logged by:          Dominik Dorn
Email address:      dominik <at> dominikdorn.com
PostgreSQL version: 9.1.10
Operating system:   Ubuntu x64
Description:        

Hi,

I ran into an issue trying to restore a custom dump from postgresql 9.1.10
from one machine into postgresql 9.1.10 on my CI machine. 

For some reason, pg_dump inserts an entry with null values into the dump
(even for the primary key). 

The commands I used are:

pg_dump -Fc -f dump.sql mydatabase (on the source machine)

pg_restore -e -d mydatabase_2013_11_05 dump.sql 

The error I get is:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 3370; 0 61665 TABLE DATA
lytartist lyriks
pg_restore: [archiver (db)] COPY failed for table "lytartist": ERROR:  null
value in column "nartistnr" violates not-null constraint
CONTEXT:  COPY lytartist, line 21841: "\N	\N	\N	\N	\N	\N	\N	\N	\N	\N	\N"
pg_restore: [archiver] worker process failed: exit code 1

the table in question looks like this:

lyriks=> \d lyriks.lytartist
                                           Table "lyriks.lytartist"
     Column     |            Type             |                          
Modifiers                           
----------------+-----------------------------+---------------------------------------------------------------
 nartistnr      | integer                     | not null default
nextval('lytartist_nartistnr_seq'::regclass)
 sartist        | character varying(250)      | not null default
''::character varying
 nartistnralias | integer                     | 
 nstatusnr      | integer                     | not null default 1660
 ntypenr        | integer                     | not null default 510
 surl           | character varying(250)      | not null default
''::character varying
 nlabelnr       | integer                     | 
 nusernr        | integer                     | not null default 0
 dnow           | timestamp without time zone | not null
 ssoundex       | character varying(250)      | 
 surlname       | character varying(100)      | 

Of course, querying for the entry with a NULL PK results in no results on
the source machine.

Please help!

Thanks,
Dominik

--

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


Gmane