From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: As superuser I still can't update a row in one table |
Date: | 2017-04-24 15:41:17 |
Message-ID: | CABzCKRCEM6wEUVrO2w1+OxWN+DopNWR8TdOdG--WMWxus0twkw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks for that pointer David. There was, indeed, a trigger on the table
which called a function raising an exception. I just have never seen that
prior to this database.
On Mon, Apr 24, 2017 at 11:21 AM, John Scalia <jayknowsunix(at)gmail(dot)com>
wrote:
> Ah,, I hadn't considered a trigger that could be blocking it. I'll look
> for it.
>
> On Mon, Apr 24, 2017 at 11:13 AM, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Mon, Apr 24, 2017 at 8:02 AM, John Scalia <jayknowsunix(at)gmail(dot)com>
>> wrote:
>>
>>> ERROR: Permission denied: UPDATE is not allowed on rhnpackageevr
>>>
>>>
>> That doesn't look like a system generated message (and grep on the
>> source tree turns up no results) - which means you should be looking for a
>> trigger that is blocking you.
>>
>> David J.
>>
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gone, Sajan | 2017-04-27 19:38:26 | Unable to start postgres instance. |
Previous Message | John Scalia | 2017-04-24 15:21:25 | Re: As superuser I still can't update a row in one table |