Re: pg_file_settings view vs. Windows - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_file_settings view vs. Windows
Date
Msg-id 19349.1435447243@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_file_settings view vs. Windows  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: pg_file_settings view vs. Windows  (Michael Paquier <michael.paquier@gmail.com>)
Re: pg_file_settings view vs. Windows  (Tatsuo Ishii <ishii@postgresql.org>)
Re: pg_file_settings view vs. Windows  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Tatsuo Ishii <ishii@postgresql.org> writes:
>> I noticed that in EXEC_BACKEND builds (ie, Windows) the pg_file_settings
>> view doesn't act as its author presumably intended.  Specifically, it
>> reads as empty until/unless the current session processes a SIGHUP event.

> I'm just wondering why we did not catch this earlier. If this is
> because threre's no regression test case for pg_file_settings view,

Yeah, exactly.  Unfortunately I see no way to add a useful test, at least
not one that will work in installcheck mode.  There's no way to predict
what will be in the view in that case.  Even for "make check", the output
would be pretty darn environment-dependent.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: pg_file_settings view vs. Windows
Next
From: Tatsuo Ishii
Date:
Subject: Refactoring pgbench.c