| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_file_settings view vs. Windows |
| Date: | 2015-06-27 23:20:43 |
| Message-ID: | 19349.1435447243@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <ishii(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2015-06-28 00:10:39 | Refactoring pgbench.c |
| Previous Message | Tatsuo Ishii | 2015-06-27 23:13:08 | Re: pg_file_settings view vs. Windows |