John R Pierce wrote:
chris wood wrote:
At a detailed level (which is NOT the direction I want this thread to
go) I do not agree with your statement that my proposal has no “hope
of ACID compliance or transactional integrity”. When the “slices” are
stored back to the cloud, this is the equivale
Gevik Babakhani wrote:
> My apologies on this late reply.
> The way LC_MESSAGES is handled on windows is much less efficient and faulty.
> While ago I started with a patch to fix some of the issues I encountered on
> windows and LC_MESSAGES. But I stopped working on that patch because this
> probl
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > Thomas H. wrote:
> >> so at least that explains the "changed" behaviour. nevertheless,
> >> LC_MESSAGES seems to be defunct - with the "locale" folder present,
> >> pg always picks the os' language and ignores the lc_message value.
chris wood wrote:
At a detailed level (which is NOT the direction I want this thread to
go) I do not agree with your statement that my proposal has no “hope
of ACID compliance or transactional integrity”. When the “slices” are
stored back to the cloud, this is the equivalent of a commit and the
> yet you propose dumbing down the database even farther, without any hope
of ACID
> compliance, without any transactional integrity, indeed, without even
really being
> relational ?
> at least, thats what I get from my first read of it.
OK so you are a theorist/perfectionist, I can respect
Where are we on this?
---
Richard Evans wrote:
> Running make inside the msys shell, I get:
>
> /c/misc/mingw/bin
> c:/misc/mingw/bin
> /c/misc/mingw/bin
>
> running inside a plain DOS command window, I get:
>
> /mingw/bi
Tom Lane wrote:
"Eugene Pimenov" <[EMAIL PROTECTED]> writes:
2) Write a code to every translation (e.g. Error 424242 inccorrect ...), so
people can actually google out a solution for their problems.
RTFM:
http://www.postgresql.org/docs/8.3/static/errcodes-appendix.html
PostgreSQL error codes
