| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Keary Suska <hierophant(at)pcisys(dot)net> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Bug or ? |
| Date: | 2005-09-06 20:38:52 |
| Message-ID: | 20357.1126039132@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Keary Suska <hierophant(at)pcisys(dot)net> writes:
> on 9/5/05 6:51 PM, tgl(at)sss(dot)pgh(dot)pa(dot)us purportedly said:
>> In any case, AFAICS this would only be an issue if you do
>> "su postgres -c postmaster" rather than "su -l postgres -c postmaster"
>> and the former is to be avoided for many reasons besides this one.
> I guess this becomes a bug report for the Darwin startup script in contrib,
> which is broken not only because it does what you recommend against (above),
> but it is also broken in other ways. How does one go about reporting this? I
> am not sure who is responsible for contrib stuff.
Whoever's using it ;-). Feel free to send a patch to pgsql-patches.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vlad | 2005-09-06 20:57:56 | Re: "select ..... for update of ..." doesn't support full qualified table name? |
| Previous Message | Tom Lane | 2005-09-06 20:28:13 | Re: "select ..... for update of ..." doesn't support full qualified table name? |