Re: [HACKERS] postgres messages error

Alvaro Herrera writes: > A quick grep reveals also > initdb.po:msgid "%s: could not to allocate SIDs: error code %lu\n" Good catch, I'll get that one too. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your su

Re: [HACKERS] postgres messages error

Tom Lane wrote: > Adam Brightwell writes: > > Martin, > > #: libpq/auth.c:1593 > >> #, fuzzy, c-format > >> msgid "could not to look up local user ID %ld: %s" > >> > >> It looks like there is an extra *to* there , so the string should be: > >> > >> "could not look up local user ID %ld: %s" > >

Re: [HACKERS] postgres messages error

Adam Brightwell writes: > Martin, > #: libpq/auth.c:1593 >> #, fuzzy, c-format >> msgid "could not to look up local user ID %ld: %s" >> >> It looks like there is an extra *to* there , so the string should be: >> >> "could not look up local user ID %ld: %s" > I think you are right. FWIW, I have

Re: [HACKERS] postgres messages error

Martin, #: libpq/auth.c:1593 > #, fuzzy, c-format > msgid "could not to look up local user ID %ld: %s" > > It looks like there is an extra *to* there , so the string should be: > > "could not look up local user ID %ld: %s" > I think you are right. FWIW, I have attached a patch that fixes it for

[HACKERS] postgres messages error

Hi there, I was doing some translation on postgres.po and found a string which looks mistaken. #: libpq/auth.c:1593 #, fuzzy, c-format msgid "could not to look up local user ID %ld: %s" It looks like there is an extra *to* there , so the string should be: "could not look up local user ID %ld: %