Re: Different transaction log for database/schema

> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of John R Pierce
> Sent: Monday, July 22, 2013 2:32 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Different transaction log for database/schema
>
> On 7/22/2013 9:33 AM, Ondrej Chaloupka wrote:
> > thank you for the idea. I didn't know about the function.
> > Just this probably won't work for my use case. I do not access to
> > different databases in one transaction. I access different databases
> > simultaneously each with it's own xa transaction. What I understand
> > the switch_xlog servers for using new file for transaction log. What I
> > would understand is supposed to be used e.g. for cleaning.
>
> postgres servers don't really have a 'transaction log' in the same sense
> as Oracle etc. they have a 'write-ahead log' which works quite
> differently.
>
> in the context of postgres's WAL logs, your question doesn't make any sense
> at all.
>
>
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>

Oracle doesn't have transaction log either, MVCC implemented through Redo Logs and Undo tablespaces, and those are per database, not per schema.
On the other hand, MS SQL Server has Transaction Logs, and they are per database.

Still, I don't quite understand, what goal original poster is trying to achieve.

Regards,
Igor Neyman