Re: Git cvsserver serious issue

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, 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 12:13:02
Message-ID: 4CAF0ACE.9000405@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

On 10/08/2010 02:09 AM, Magnus Hagander wrote:
> On Fri, Oct 8, 2010 at 03:52, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>>
>> There's a simpler solution which I have just tested. Instead of patching,
>> use the Pg driver instead of SQLite. Set the dbname to %m. If the database
>> doesn't exist the cvs checkout will fail. So we just set up databases for
>> the modules we want to export (master and RELn_m_STABLE for the live
>> branches).
> A database per branch seems like a horrible idea in general, but if it
> works us around the bug, it seems like a doable idea.. As long as
> we'll never have a branch called "postgres" or "git" (already in use
> on that box).
>
> I'll look into it.

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.

cheers

andrew

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Marko Kreen 2010-10-08 13:15:46 Re: Git cvsserver serious issue
Previous Message Magnus Hagander 2010-10-08 06:09:26 Re: Git cvsserver serious issue

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-10-08 13:06:10 Re: standby registration (was: is sync rep stalled?)
Previous Message Vincenzo Romano 2010-10-08 10:20:14 Re: On Scalability