Re: Git cvsserver serious issue - Mailing list pgsql-hackers

From Aidan Van Dyk
Subject Re: Git cvsserver serious issue
Date
Msg-id AANLkTimi81Oc7mAruPDWN9B0Yw3+_byxAZO4dXjuJvNG@mail.gmail.com
Whole thread Raw
In response to Re: Git cvsserver serious issue  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Git cvsserver serious issue
List pgsql-hackers
On Fri, Oct 8, 2010 at 8:13 AM, Andrew Dunstan <andrew@dunslane.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@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Issues with Quorum Commit
Next
From: Fujii Masao
Date:
Subject: Re: Issues with Quorum Commit