Re: Git cvsserver serious issue

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git cvsserver serious issue
Date: 2010-10-08 14:53:20
Message-ID: AANLkTimi81Oc7mAruPDWN9B0Yw3+_byxAZO4dXjuJvNG@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

On Fri, Oct 8, 2010 at 8:13 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

> That's what the default SQLite setup does anyway. The only difference here
> is that we are leveraging the fact that with the Pg driver the database must
> first exist. Of course, with Pg the database can live on a different host or
> in a server run on a different port, if you need to avoid naming conflicts.

That can be done in SQLite to, just set the "database name" to a path
where there is no create access. Pre-create the database, and don't
let SQLite "create" new ones every time they are accessed. Standard
unix permissins should easily allow that setup. chmod -w on the
directory the database files go in.

a.

--
Aidan Van Dyk                                             Create like a god,
aidan(at)highrise(dot)ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2010-10-08 15:03:02 Re: Git cvsserver serious issue
Previous Message Andrew Dunstan 2010-10-08 13:18:27 Re: Git cvsserver serious issue

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-10-08 14:55:49 Re: Issues with Quorum Commit
Previous Message Fujii Masao 2010-10-08 14:48:54 Re: Issues with Quorum Commit