Re: PQputline error with pg_restore

<div>The postmaster stderr was being sent to /dev/null, so I changed
that and was able to generate a log file.&nbsp; 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 thing and would greatly appreciate any
help.&nbsp; Here's the info from the log:<br>
<br>
postmaster successfully started<br>
LOG:&nbsp; database system was shut down at 2006-02-09 15:37:30 EST<br>
LOG:&nbsp; checkpoint record is at 1/2C118B80<br>
LOG:&nbsp; redo record is at 1/2C118B80; undo record is at 0/0; shutdown TRUE<br>
LOG:&nbsp; next transaction id: 6659; next oid: 19331162<br>
LOG:&nbsp; database system is ready<br>
WARNING:&nbsp; Attribute "piece" has an unknown type<br>
&nbsp;&nbsp;&nbsp; Proceeding with relation creation anyway<br>
WARNING:&nbsp; Attribute "piece" has an unknown type<br>
&nbsp;&nbsp;&nbsp; Proceeding with relation creation anyway<br>
LOG:&nbsp; recycled transaction log file 000000010000002B<br>
LOG:&nbsp; recycled transaction log file 000000010000002C<br>
LOG:&nbsp; recycled transaction log file 000000010000002D<br>
LOG:&nbsp; recycled transaction log file 000000010000002E<br>
LOG:&nbsp; recycled transaction log file 000000010000002F<br>
LOG:&nbsp; recycled transaction log file 0000000100000030<br>
LOG:&nbsp; recycled transaction log file 0000000100000031<br>
LOG:&nbsp; recycled transaction log file 0000000100000032<br>
LOG:&nbsp; recycled transaction log file 0000000100000033<br>
LOG:&nbsp; recycled transaction log file 0000000100000034<br>
ERROR:&nbsp; copy: line 178286, overflow on numeric ABS(value) &gt;= 10^3 for field with precision 5 scale 3<br>
FATAL:&nbsp; Socket command type 8 unknown<br>
LOG:&nbsp; recycled transaction log file 0000000100000036<br>
LOG:&nbsp; recycled transaction log file 0000000100000037<br>
LOG:&nbsp; recycled transaction log file 0000000100000035<br>
<br>
Thanks,<br>
Jennifer<br>
<br></div><font color="#990099">-----pgsql-general-owner(at)postgresql(dot)org wrote: -----<br>
</font><blockquote style="border-left: 2px solid rgb(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 more info about the error, but<br>unfortunately that release of pg_restore isn't going to tell you what<br>the error message from PQputline is. &nbsp;So you'll have to try to find<br>out from the postmaster's log.<br><br>You'll need to look at 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 :-(. &nbsp;You can change the<br>script to redirect to some real file and then restart the postmaster and<br>then try the restore again. &nbsp;Or reconfigure things so that the<br>postmaster sends its 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, that file will continue to grow as long as the<br>postmaster runs.)<br><br>Once you've managed to see the underlying error 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. &nbsp;psql will probably<br>be more cooperative about showing the underlying message.<br><br><span style="visibility: hidden;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="visibility: hidden;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="visibility: hidden;">&nbsp;&nbsp;&nbsp;&nbsp;</span> regards, tom lane<br><br>
</font></blockquote><br>