From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] pg crashing |
Date: | 2008-07-02 23:06:04 |
Message-ID: | 17797.1215039964@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> below this is going to convert \ to /, wouldn't it be clearer to
>> describe the path prefix as Global/PostgreSQL: in the first place?
> Eh, that shows another bug I think. It should *not* convert the \ in
> "Global\", because that one is is interpreted by the Win32 API call!
I was wondering about that. What are the implications of that?
> I think it should be per this patch. Seems right?
Pls fix the comment on the malloc, too.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Magoffin | 2008-07-02 23:19:25 | Re: Memory use in 8.3 plpgsql with heavy use of xpath() |
Previous Message | Kris Jurka | 2008-07-02 22:25:39 | Re: Memory use in 8.3 plpgsql with heavy use of xpath() |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2008-07-02 23:11:01 | WITH RECURSIVE updated to CVS TIP |
Previous Message | Dave Page | 2008-07-02 21:50:31 | Re: Working on native Windows x64 version of PostgreSQL |