Re: Unwanted LOG during recovery of DROP TABLESPACE REDO

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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-07-16 14:33:16
Message-ID: 26294.1405521196@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-07-16 14:51:50 Re: Allowing join removals for more join types
Previous Message Andres Freund 2014-07-16 14:24:31 Re: Pg_upgrade and toast tables bug discovered