Craig James wrote:
> Alvaro Herrera wrote:
>> To recap:
>>
>> - your app only does inserts
>> - there has been no rollback lately
>> - there are no updates
>> - there are no deletes
>>
>> The only other source of dead rows I can think is triggers ... do you
>> have any? (Not necessarily on this table -- perhaps triggers on other
>> tables can cause updates on this one).
>>
>> Oh, rolled back COPY can cause dead rows too.
>
>
> What about an unreliable network that causes lot of disconnects?
> Wouldn't the server process do a rollback?
>
Perhaps in theory, but in practice my client and the postgreSQL servers are
on the same machine and the 127.0.0.1 is pretty reliable:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:30097919 errors:0 dropped:0 overruns:0 frame:0
TX packets:30097919 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:931924602 (888.7 MiB) TX bytes:931924602 (888.7 MiB)
--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 22:10:01 up 22 days, 15:28, 0 users, load average: 4.25, 4.21, 4.12
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
