| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Thomas Hallgren <thhal(at)mailblocks(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: bug in GUC |
| Date: | 2004-06-24 17:29:13 |
| Message-ID: | 20709.1088098153@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> I'm not sure exactly why this is a good idea. After all, if the systems
> runs out of memory while starting up, what can be expected later?
The issue isn't with startup, but with re-reading postgresql.conf due to
SIGHUP later on. We don't want to elog(ERROR) partway through that
process. Especially not in the postmaster, where elog(ERROR) is
tantamount to elog(FATAL). (But of course the postmaster shouldn't ever
run out of memory anyway...)
It's possible that this should all be rethought, but it would be a much
more wide-ranging change than we've been discussing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2004-06-27 18:45:40 | Re: [HACKERS] bug in GUC |
| Previous Message | Alvaro Herrera | 2004-06-24 16:55:42 | Re: bug in GUC |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mary Edie Meredith | 2004-06-24 17:34:03 | Re: DBT-2 results using tablespaces |
| Previous Message | Tom Lane | 2004-06-24 17:13:42 | Re: [Re] Re: PREPARE and transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-06-24 18:38:56 | Re: pg_ctl service integration for WIN32 |
| Previous Message | Alvaro Herrera | 2004-06-24 16:55:42 | Re: bug in GUC |