Re: Different transaction log for database/schema - Mailing list pgsql-general

From Luca Ferrari
Subject Re: Different transaction log for database/schema
Date
Msg-id CAKoxK+77hFsKKQ6FqVO8Q5wTo+7xX-hDfgZ6u9BmD-can=vpiA@mail.gmail.com
Whole thread Raw
In response to Different transaction log for database/schema  ("Ondrej Chaloupka" <chalda@seznam.cz>)
List pgsql-general
On Mon, Jul 22, 2013 at 10:09 AM, Ondrej Chaloupka <chalda@seznam.cz> wrote:
> Hello,
>
> I would like kindly ask for an advice whether and how the transaction log
> behavior could be configured.
>
> I would like to have possibility to differentiate transaction logs for two
> databases or schema. I would need such configuration for my testing
> environment where I need to run simultaneously different tests using
> transactions. And I need to separate those tests for being sure that they do
> not interfere with each other. I'm using XA transactions in Java.


It is not clear to me to which logs you are referring: the commit logs
or the WALs? Anyway, transaction are numbered in an unique way around
the cluster, and therefore it does not matter on which database you
are going to run the transaction, it will not interfere with other
databases within the same cluster.
I don't get what advantage will give you having logs different for
each database/schema, considering that it is not clear what kind of
maintenance you are going to do on such logs. Can you please better
explain what is your aim and use case?

Luca


pgsql-general by date:

Previous
From: Amit Langote
Date:
Subject: Re: maintenance_work_mem and CREATE INDEX time
Next
From: Ian Lawrence Barwick
Date:
Subject: Viewing another role's search path?