On 2013-09-08 20:00:58 +0200, Daniel Vérité wrote: > Or is there a simpler way to deal with the above case?
One would be to use open(O_NOFOLLOW)? But more generally I am of the opinion that it's the superusers responsibility to make sure that cannot happen by only using properly secured files. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers