>
> And it's been a while; but I thought transactions like that could
> overflow rollback segments in that other database.
>
ORA-01555: snapshot too old: rollback segment number string with name
"string" too small
Cause: Rollback records needed by a reader for consistent read are
overwritten
Greg Stark wrote:
Well it's worse than that. If you have long-running transactions that would
cause rollback-segment-overflow in Oracle then the equivalent price in
Postgres would be table bloat *regardless* of how frequently you vacuum.
Isn't that a bit pessimistic? In tables which mostly gr
Tom Lane <[EMAIL PROTECTED]> writes:
> Of course, there's no free lunch --- the price we pay for escaping
> rollback-segment-overflow is table bloat if you don't vacuum often
> enough.
Well it's worse than that. If you have long-running transactions that would
cause rollback-segment-overflow in
> Please, what is the meaning of 'AIUI' ..
This site was a big help for me as acronyms are popular on this list:
http://www.acronymfinder.com
Regards,
Richard
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Mon, Mar 13, 2006 at 04:51:03PM +0100, Agnes Bocchino wrote:
> Please, what is the meaning of 'AIUI' ..
As I Understand It
--
Martijn van Oosterhout http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and
Martijn van Oosterhout wrote:
On Mon, Mar 13, 2006 at 03:59:33PM +0100, Agnes Bocchino wrote:
I would like to know how Postgresql works when all the files
(checkpoint_segment *2 + 1)
are full ,
does Postgresql rollback the transaction when all the wal segments are used,
or does the server s
Martijn van Oosterhout writes:
> On Mon, Mar 13, 2006 at 03:59:33PM +0100, Agnes Bocchino wrote:
>> (I have tried to make the test but without success for finding a long
>> transaction)
> AIUI it just keeps creating more segments. i.e. checkpoint_segment is
> not a hard limit. It's just the numbe
On Mon, Mar 13, 2006 at 03:59:33PM +0100, Agnes Bocchino wrote:
> I would like to know how Postgresql works when all the files
> (checkpoint_segment *2 + 1)
> are full ,
> does Postgresql rollback the transaction when all the wal segments are used,
> or does the server stop with an error message ?
I would like to know how Postgresql works when all the files
(checkpoint_segment *2 + 1)
are full ,
does Postgresql rollback the transaction when all the wal segments are used,
or does the server stop with an error message ?
(I have tried to make the test but without success for finding a long
t
