| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| 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 15:03:02 |
| Message-ID: | 4CAF32A6.6090705@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members pgsql-hackers |
On 10/08/2010 10:53 AM, Aidan Van Dyk wrote:
> 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.
*shrug*. We are the PostgreSQL project after all :-) But whatever Magnus
wants to do is OK with me.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-10-12 19:57:01 | Re: Git cvsserver serious issue |
| Previous Message | Aidan Van Dyk | 2010-10-08 14:53:20 | Re: Git cvsserver serious issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2010-10-08 15:06:26 | Re: Issues with Quorum Commit |
| Previous Message | Simon Riggs | 2010-10-08 14:57:21 | Re: Issues with Quorum Commit |