From: | Giles Thomas <giles(at)pythonanywhere(dot)com> |
---|---|
To: | Christoph Berg <cb(at)df7cb(dot)de>, pgsql-pkg-debian(at)postgresql(dot)org, "support(at)pythonanywhere(dot)com" <support(at)pythonanywhere(dot)com> |
Subject: | Re: Odd table ownership for PostgreSQL |
Date: | 2013-07-31 18:03:14 |
Message-ID: | 51F95162.4000102@pythonanywhere.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
Hi there,
On 27/07/2013 13:37, Christoph Berg wrote:
> Re: Giles Thomas 2013-07-26 <51F2B37E(dot)5070501(at)pythonanywhere(dot)com>
>> We're installing PostgreSQL to Ubuntu raring machines using the
>> http://apt.postgresql.org/pub/repos/apt/ PPA. Something strange
>> seems to have happened at some point after 19:39 UTC on 23 July.
>>
>> Details of the error are here <http://dba.stackexchange.com/questions/47005/postgresql-create-table-creates-with-incorrect-owner>
>> but to summarise, we're creating a user, creating a database owned
>> by that user, and then as that user we're creating a table in the
>> database. The new table turns out to be owned by user postgres
>> rather than by the new user. The new user does not have (but can
>> grant himself) permissions on the table.
>>
>> This problem is not present on a machine that installed PostgreSQL
>> from the PPA at 19:39 UTC on 23 July. But it is present in one that
>> installed it at 13:16 UTC on 24 July, and in every machine we've
>> installed it on since.
>>
>> Any help would be much appreciated!
> Nothing has changed on apt.postgresql.org since July 22nd, so this is
> not caused by a packaging change. I cannot reproduce the problem using
> 9.2.4-1.pgdg+1 on sid/amd64.
>
> Is there any pooler between you and the database that might be messing
> up with the current user?
Apologies for taking up your bandwith with this one, it turns out that
there was one other factor involved that we'd forgotten -- we were using
PostgreSQL Extension Whitelist extension
(<https://github.com/dimitri/pgextwlist/>) and we've confirmed that the
problem is present iff that extension is installed. It looks like it
was last updated on 23 July, so I think we've found our culprit.
All the best, and thanks very much for getting back to us on this.
Giles
--
Giles Thomas <giles(at)pythonanywhere(dot)com>
PythonAnywhere: Develop and host Python from your browser
<http://pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
From | Date | Subject | |
---|---|---|---|
Next Message | Colin 't Hart | 2013-08-01 08:48:30 | pg_createcluster not obeying default for socket directory |
Previous Message | Christoph Berg | 2013-07-27 12:37:30 | Re: Odd table ownership for PostgreSQL |