Re: PQputline error with pg_restore - Mailing list pgsql-general

<div>The postmaster stderr was being sent to /dev/null, so I changed that and was able to generate a log file. 
Unfortunately,I'm not sure what the output in the log file means - I don't have a lot of experience with this sort of
thingand would greatly appreciate any help.  Here's the info from the log:<br /><br /> postmaster successfully
started<br/> LOG:  database system was shut down at 2006-02-09 15:37:30 EST<br /> LOG:  checkpoint record is at
1/2C118B80<br/> LOG:  redo record is at 1/2C118B80; undo record is at 0/0; shutdown TRUE<br /> LOG:  next transaction
id:6659; next oid: 19331162<br /> LOG:  database system is ready<br /> WARNING:  Attribute "piece" has an unknown
type<br/>     Proceeding with relation creation anyway<br /> WARNING:  Attribute "piece" has an unknown type<br />    
Proceedingwith relation creation anyway<br /> LOG:  recycled transaction log file 000000010000002B<br /> LOG:  recycled
transactionlog file 000000010000002C<br /> LOG:  recycled transaction log file 000000010000002D<br /> LOG:  recycled
transactionlog file 000000010000002E<br /> LOG:  recycled transaction log file 000000010000002F<br /> LOG:  recycled
transactionlog file 0000000100000030<br /> LOG:  recycled transaction log file 0000000100000031<br /> LOG:  recycled
transactionlog file 0000000100000032<br /> LOG:  recycled transaction log file 0000000100000033<br /> LOG:  recycled
transactionlog file 0000000100000034<br /> ERROR:  copy: line 178286, overflow on numeric ABS(value) >= 10^3 for
fieldwith precision 5 scale 3<br /> FATAL:  Socket command type 8 unknown<br /> LOG:  recycled transaction log file
0000000100000036<br/> LOG:  recycled transaction log file 0000000100000037<br /> LOG:  recycled transaction log file
0000000100000035<br/><br /> Thanks,<br /> Jennifer<br /><br /></div><font
color="#990099">-----pgsql-general-owner@postgresql.orgwrote: -----<br /></font><blockquote style="border-left: 2px
solidrgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"><font face="monospace"
size="3"><br/>You should really update to something more current than 7.3.2 :-(<br /><br />The first thing to do is get
moreinfo about the error, but<br />unfortunately that release of pg_restore isn't going to tell you what<br />the error
messagefrom PQputline is.  So you'll have to try to find<br />out from the postmaster's log.<br /><br />You'll need to
lookat the startup script Mandrake uses for postgres<br />to see where it sends the postmaster's stderr, but I wouldn't
be<br/>surprised to find that it sends to /dev/null :-(.  You can change the<br />script to redirect to some real file
andthen restart the postmaster and<br />then try the restore again.  Or reconfigure things so that the<br />postmaster
sendsits log messages to syslog --- though this may take<br />some fooling with syslog's configuration as well as with
postgresql.conf.<br/>(Syslog is probably a better choice for production purposes --- if you<br />redirect to a file,
thatfile will continue to grow as long as the<br />postmaster runs.)<br /><br />Once you've managed to see the
underlyingerror message, if it doesn't<br />make things clear then pass the info along and we'll try to help.<br /><br
/>BTW,another thing you could try is having pg_restore just generate<br />a SQL script, and then feed the SQL script to
psql. psql will probably<br />be more cooperative about showing the underlying message.<br /><br /><span
style="visibility:hidden;">    </span><span style="visibility: hidden;">    </span><span style="visibility:
hidden;">    </span>regards, tom lane<br /><br /></font></blockquote><br />