Re: Git cvsserver serious issue
От
Aidan Van Dyk
Тема
Re: Git cvsserver serious issue
Дата
Msg-id
AANLkTimi81Oc7mAruPDWN9B0Yw3+_byxAZO4dXjuJvNG@mail.gmail.com
Ответ на
Re: Git cvsserver serious issue (Andrew Dunstan)
Список
Дерево обсуждения
Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Peter Eisentraut <peter_e@gmx.net>
Re: Git cvsserver serious issue Alvaro Herrera <alvherre@commandprompt.com>
Re: Git cvsserver serious issue Abhijit Menon-Sen <ams@toroid.org>
Re: Git cvsserver serious issue Robert Haas <robertmhaas@gmail.com>
Re: Git cvsserver serious issue Tom Lane <tgl@sss.pgh.pa.us>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Tom Lane <tgl@sss.pgh.pa.us>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Bruce Momjian <bruce@momjian.us>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Bruce Momjian <bruce@momjian.us>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue David Fetter <david@fetter.org>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue David Fetter <david@fetter.org>
Re: Git cvsserver serious issue Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: Git cvsserver serious issue Tom Lane <tgl@sss.pgh.pa.us>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Tom Lane <tgl@sss.pgh.pa.us>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Tom Lane <tgl@sss.pgh.pa.us>
Re: Git cvsserver serious issue Aidan Van Dyk <aidan@highrise.ca>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Marko Kreen <markokr@gmail.com>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Aidan Van Dyk <aidan@highrise.ca>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
Re: Git cvsserver serious issue Magnus Hagander <magnus@hagander.net>
Re: Git cvsserver serious issue Andrew Dunstan <andrew@dunslane.net>
On Fri, Oct 8, 2010 at 8:13 AM, Andrew Dunstan 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 по дате отправления