Rajeev rastogi <rajeev.rast...@huawei.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

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to