Re: Git cvsserver serious issue

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: Git cvsserver serious issue
Дата
Msg-id 4CAF0ACE.9000405@dunslane.net
обсуждение исходный текст
Ответ на Re: Git cvsserver serious issue  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Git cvsserver serious issue  (Marko Kreen <markokr@gmail.com>)
Re: Git cvsserver serious issue  (Aidan Van Dyk <aidan@highrise.ca>)
Список pgsql-hackers

On 10/08/2010 02:09 AM, Magnus Hagander wrote:
> On Fri, Oct 8, 2010 at 03:52, Andrew Dunstan<andrew@dunslane.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Vincenzo Romano
Дата:
Сообщение: Re: On Scalability
Следующее
От: Robert Haas
Дата:
Сообщение: Re: standby registration (was: is sync rep stalled?)