From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Rajeev rastogi" <rajeev(dot)rastogi(at)huawei(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unwanted LOG during recovery of DROP TABLESPACE REDO |
Date: | 2014-08-25 15:04:50 |
Message-ID: | 53FB5092.4010603@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/15/2014 12:31 PM, Marko Tiikkaja wrote:
> On 7/16/14 4:33 PM, Tom Lane wrote:
>> Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com> writes:
>>> I found and fixed a bug that causes recovery (crash recovery , PITR) to throw unwanted LOG message if the tablespace symlink is not found during the processing of DROP TABLESPACE redo.
>>> LOG: could not remove symbolic link "pg_tblspc/16384": No such file or directory
>>
>> I don't think that's a bug: it's the designed behavior. Why should we
>> complicate the code to not print a log message in a situation where
>> it's unclear if the case is expected or not?
>
> I agree with Tom here; this doesn't seem like an improvement.
Well, for comparison, we also silently ignore non-existent files when
replaying a "DROP TABLE". I could go either way myself, but this is
clearly a very minor thing, and we have two -1's, so I'm marking this as
"Rejected" in the commitfest.
Thanks anyway!
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-08-25 15:14:02 | Re: Allow multi-byte characters as escape in SIMILAR TO and SUBSTRING |
Previous Message | Heikki Linnakangas | 2014-08-25 14:51:51 | Re: Allow multi-byte characters as escape in SIMILAR TO and SUBSTRING |