Re: hstore extension version screwup

From: Jim Nasby <jim(at)nasby(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: hstore extension version screwup
Date: 2013-10-02 17:17:52
Message-ID: 524C5540.1020104@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/29/13 9:41 PM, Andrew Dunstan wrote:
>
> On 09/29/2013 10:38 PM, Peter Eisentraut wrote:
>> On Sun, 2013-09-29 at 22:33 -0400, Andrew Dunstan wrote:
>>> Well if these are not meant to be changed then not being able to write
>>> them in your git repo might be a clue to that.
>> Git doesn't support setting file permissions other than the executable
>> bit, so this is a nonstarter.
>>
>
> Oh, didn't know that, I've certainly know other SCM systems that do.

We could potentially do it with git commit hooks, but the problem is that there's no way to force use of those on clients (a huge deficiency in git, imho).

The best alternative I've been able to come up with is having hooks in a standard location in the repo and then there's one file that people would need to put into their home directory (under ~/.git I think) that would pull all of that stuff in.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2013-10-02 17:45:24 Re: [HACKERS] Who is pgFoundery administrator?
Previous Message Pavel Stehule 2013-10-02 17:05:59 Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL