No, it's super frustrating. While I do the recovery, it says it reaches a
consistent recovery state, and i just cannot find a way how to convince pg
to stop at that state:
2013-08-02 09:23:25 GMT DEBUG: postgres: PostmasterMain: initial
environment dump:
2013-08-02 09:23:25 GMT DEBUG:
Isn't it a funny coincidence, that we also had a corruption of that
same/similar type?
my disk was quite confidently not tampered. I am wondering: Does PG sign,
or checksum wal_files? Is the integrity of wal_files ensured by any
mechanism? Because if it IS, then - in our case - it's a corruption c
ally vague. I cannot really grasp the problem
myself, this is why my description might be lacking detail.
I will cross-post to 'general'
thx,k
On Mon, Jul 29, 2013 at 11:38 PM, Greg Stark wrote:
> On Mon, Jul 29, 2013 at 10:19 PM, Klaus Ita wrote:
> > My feeling is, that
Hi list!
depressed me gets error messages like these:
2013-07-29 20:57:09 UTC ERROR: could not access
status of transaction 8393477
2013-07-29 20:57:09 UTC DETAIL: Could not open
file "pg_clog/0008": No such file or directory.
combined with the error output of queries that do not work.
I l
nyway, there cannot be any lower for SS that maps it to ß, that would
require knowledge of the word at least.
and I just tried in the different programming languages i know (which is
by far not enough) but in java, eg when you use the javac from sun, it
actually works the way i say.
i will add
I know that tom is going to say this is not a bug in pg and he is probably
right. but still i want to state, that in pg 8.1 the
select lower(upper('ß'))
does not return 'ss'. because the upper('ß') does not return 'SS' in the
first place. I know, german is a terrible language, but still - we are
On Sun, Jun 18, 2006 at 07:38:13PM +0530, vinayak Desai wrote:
> [EMAIL PROTECTED] ~]# createuser -a -d -e antonio
> createuser: could not connect to database template1: FATAL: user "root"
> does not exist
> [EMAIL PROTECTED] ~]#
>
> i logged in as root..
> I tried to create a new user i am getti
On Thu, Sep 01, 2005 at 09:30:15AM -0400, Tom Lane wrote:
> Klaus Ita <[EMAIL PROTECTED]> writes:
> > I have tried starting postgres with [EMAIL PROTECTED]
> > locale but that did not help.
>
i did read the docs and am still not quite happy with my sorting results.
Hi there!
I have a Problem with a DB that was created in UNICODE
* createdb -E UNICODE
and actually shows that it _is_ in UNICODE.
i was able to input data and can read it and everything is fine.
but when i want to "ORDER BY ..." it does not sort the german Umlauts at the
correct postition.
sho
hi all!
i am using version 7.4.7/Debian of postgres.
as far as i understand the standard, the following situation should not
be possible. neither is it stated in the manual that the select is not
conforming to the standard.
i have the following data:
table L:
LNR ORT LCODE MENGE
L1
hi all!
sorry if you are recieving this twice, i amm too stupid to file a simple
bugreport (3rd!!! try already)
i am using version 7.4.7/Debian of postgres.
as far as i understand the standard, the following situation should not
be possible. neither is it stated in the manual that the select is
most conforming db.
thx,
klaus
* Richard Huxton [2005-02-25 15:43:
> From: Richard Huxton
> Subject: Re: [BUGS] select clause not according to SQL standard
> To: Klaus Ita <[EMAIL PROTECTED]>
> Cc: pgsql-bugs@postgresql.org
> X-Virus-Scanned: by Amavis (ClamAV) at st
hi all!
sorry if you are recieving this 3 times, i am too stupid to file a simple
bugreport (4rd!!! try already) . btw the bugreport webinterface is
broken.
i am using version 7.4.7/Debian of postgres.
as far as i understand the standard, the following situation should not
be possible. neither i
13 matches
Mail list logo
