On 10/17/06, Martijn van Oosterhout wrote:
xlogs are recycled. You can control the growth somewhat by playing with
the xlog settings in the config. It should stabilise at about 16MB
times the wal segments.
This is very good news! Thanks,
Andras
---(end of broadcast)-
On Tue, Oct 17, 2006 at 05:54:42PM +0200, Andras Simon wrote:
> >The xlog is not split by database, all databases share the same xlog.
>
> OK, I see. The question then is how far does it grow. If its size is
> comparable to that of the actual data, then having separate
> tablespaces is not as usef
On 10/17/06, Martijn van Oosterhout wrote:
On Tue, Oct 17, 2006 at 04:56:09PM +0200, Andras Simon wrote:
> As a more drastic example: I created a DB on a tablespace TS, and
> copied a 25 MB file into one of its tables. I ended up having 60
> MB of extra data in $PGDATA/pg_xlog that doesn't go aw
On Tue, Oct 17, 2006 at 04:56:09PM +0200, Andras Simon wrote:
> As a more drastic example: I created a DB on a tablespace TS, and
> copied a 25 MB file into one of its tables. I ended up having 60
> MB of extra data in $PGDATA/pg_xlog that doesn't go away even
> after dropping the database.
The xl
It seems that PG uses the PGDATA directory even for operations
that affect databases on different tablespaces. For example, when
an index is created on a table that is in tablespace TS, the
index ends up in TS (as it should), but first a temporary
file (with size comparable to the final index) is
