initdb -S versus superuser check and Windows restricted mode - Mailing list pgsql-hackers

From Tom Lane
Subject initdb -S versus superuser check and Windows restricted mode
Date
Msg-id 4389.1432933727@sss.pgh.pa.us
Whole thread Raw
Responses Re: initdb -S versus superuser check and Windows restricted mode  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
I noticed that if you use "initdb -S", the code does its thing and
exits without ever calling get_restricted_token().  It doesn't get
to get_id() where the no-superuser check is, either.  Is this OK,
or should we reorder the operations so that fsyncing is done with
the usual restricted privileges?

You could argue that it's harmless to let root do a bunch of fsyncs,
and that's probably true, but on the other hand this doesn't meet
our usual expectations that no significant PG code runs as root.

Thoughts?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [CORE] postpone next week's release
Next
From: Josh Berkus
Date:
Subject: Re: RFC: Remove contrib entirely