| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | 'Jeff Janes' <jeff(dot)janes(at)gmail(dot)com>, 'pgsql-hackers' <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Resource Owner reassign Locks |
| Date: | 2012-06-19 06:09:41 |
| Message-ID: | 4FE017A5.9080101@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19.06.2012 09:02, Amit Kapila wrote:
>> Please take a look to see if I broke something.
> In you previous mail you agreed with level as ERROR for elog message in
> function ResourceOwnerForgetLock(..) function,
> but in your modification you have used PANIC, is there any specific reason
> for it.
Ah, sorry, that was just a debugging aid. Before posting the patch, I
had a bug (now fixed) where I got that error, and I changed it
temporarily to PANIC to get a core dump, but forgot to change it back
before posting the patch. It should indeed be ERROR, not PANIC.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-19 06:15:43 | Re: Pg default's verbosity? |
| Previous Message | Tom Lane | 2012-06-19 06:03:04 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |