| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, "Rodrigo Moreno" <rodrigo(dot)miguel(at)terra(dot)com(dot)br>, pgsql-hackers-win32(at)postgresql(dot)org |
| Subject: | Re: REPOST: InitDB Failure on install |
| Date: | 2004-08-15 21:11:00 |
| Message-ID: | 29697.1092604260@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
>> creating template1 database in F:/PostgreSQL/data/base/1 ... WARNING:
>> could
>> not find a match for Windows timezone "Hora oficial do Brasil"
>> FATAL: could not create shared memory segment: No error
>> DETAIL: Failed system call was shmget(key=1, size=1196032, 03600).
> child process was terminated by signal 1
> This is not an issue with the timezone code, this is an issue with the
> shmem code.
Well, the report does also expose a timezone problem, which we've seen
reported by other people too: apparently strftime can return non-English
names for timezones. If we want to stick with the current scheme for
detecting Windows timezone, we may have to use a far larger and uglier
mapping table than we have now :-(. Any ideas about that? Is there
a way to temporarily force strftime to speak English? Or maybe another
API besides strftime?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-08-15 21:13:50 | Re: REPOST: InitDB Failure on install |
| Previous Message | Tom Lane | 2004-08-15 21:06:35 | Re: REPOST: InitDB Failure on install |