Re: [BUGS] BUG #8514: cache lookup failed for relation 421062806

2013-10-10 Thread Michael Paquier
On Thu, Oct 10, 2013 at 1:24 AM, wrote: > my postgresql running file . but sometime i found cache lookup failed for > relation 421062806 error in postgresql log. can anyone tell me significant > of this error. A relation has disappeared even if the session hold a sufficient lock on it, ensuring t

[BUGS] PostgreSQL Service on Windows does not start.

2013-10-10 Thread Naoya Anzai
Hi All, I have found a case that PostgreSQL Service does not start. When it happens, the following error appears. "is not a valid Win32 application" This failure occurs when the following conditions are true. 1. There is "postgres.exe" in any directory that contains a space, such as "Progra

Re: [BUGS] BUG #8467: Slightly confusing pgcrypto example in docs

2013-10-10 Thread Bruce Momjian
On Thu, Oct 10, 2013 at 08:32:32PM -0400, Bruce Momjian wrote: > > > How can the later entry not be MD5 hash? > > > > Because what you pass to the functions is 'md5', not 'md5 hash', which > > is what the new text appears to indicate. > > So if we revert, will it still be clear what is MD5 and w

Re: [BUGS] BUG #8467: Slightly confusing pgcrypto example in docs

2013-10-10 Thread Bruce Momjian
On Thu, Oct 10, 2013 at 08:22:30PM -0400, Peter Eisentraut wrote: > On Thu, 2013-10-10 at 19:14 -0400, Bruce Momjian wrote: > > > The changes shown below are incorrect, I think. > > > > > > > > > On 10/2/13 12:00 PM, Bruce Momjian wrote: > > > > *** gen_salt(type text [, iter_count in

Re: [BUGS] BUG #8467: Slightly confusing pgcrypto example in docs

2013-10-10 Thread Peter Eisentraut
On Thu, 2013-10-10 at 19:14 -0400, Bruce Momjian wrote: > > The changes shown below are incorrect, I think. > > > > > > On 10/2/13 12:00 PM, Bruce Momjian wrote: > > > *** gen_salt(type text [, iter_count integer > > > *** 353,359 > > > 12 years > > > > > >

Re: [BUGS] BUG #8516: Calling VOLATILE from STABLE function

2013-10-10 Thread 'Bruce Momjian'
On Thu, Oct 10, 2013 at 04:10:35PM -0700, Dwayne Towell wrote: > > According to the documentation, f() should be marked VOLATILE also, since > > calling f() produces side effects. PostgreSQL does not give a warning (or > > better yet, an error); I think it should. > > I think the answer is that fu

Re: [BUGS] BUG #8467: Slightly confusing pgcrypto example in docs

2013-10-10 Thread Bruce Momjian
On Thu, Oct 10, 2013 at 04:05:50PM -0400, Peter Eisentraut wrote: > The changes shown below are incorrect, I think. > > > On 10/2/13 12:00 PM, Bruce Momjian wrote: > > *** gen_salt(type text [, iter_count integer > > *** 353,359 > > 12 years > > > > > >

Re: [BUGS] BUG #8516: Calling VOLATILE from STABLE function

2013-10-10 Thread Bruce Momjian
On Wed, Oct 9, 2013 at 08:58:46PM +, dwa...@docketnavigator.com wrote: > The following bug has been logged on the website: > > Bug reference: 8516 > Logged by: Dwayne Towell > Email address: dwa...@docketnavigator.com > PostgreSQL version: 9.2.4 > Operating system: CentOS

Re: [BUGS] Completely broken replica after PANIC: WAL contains references to invalid pages

2013-10-10 Thread Sergey Konoplev
On Thu, Oct 10, 2013 at 2:48 PM, Alvaro Herrera wrote: >> Could you please give me a hint of how to check if this patch was >> included in 9.2.5 or not? > > Yes, this was committed in June: > > commit 99ee15b315c187045a95db7b27fd9d866aea93e0 > Author: Simon Riggs > Date: Sun Jun 23 11:05:02 201

Re: [BUGS] Completely broken replica after PANIC: WAL contains references to invalid pages

2013-10-10 Thread Alvaro Herrera
Sergey Konoplev escribió: > On Tue, Jun 11, 2013 at 6:50 AM, Tom Lane wrote: > > Sergey Konoplev writes: > >> Just curious, what is the planned date for the next minor release, and > >> BTW where is it possible to see the roadmap for minor releases? > > > > There is no planned date, and certainly

Re: [BUGS] Completely broken replica after PANIC: WAL contains references to invalid pages

2013-10-10 Thread Sergey Konoplev
On Tue, Jun 11, 2013 at 6:50 AM, Tom Lane wrote: > Sergey Konoplev writes: >> Just curious, what is the planned date for the next minor release, and >> BTW where is it possible to see the roadmap for minor releases? > > There is no planned date, and certainly no "roadmap". We make minor > releas

Re: [BUGS] error

2013-10-10 Thread John R Pierce
On 10/10/2013 7:18 AM, Andrius Di wrote: Hello, how to solve this error (please see attachment)? what exactly were you doing when you got this error, what Windows version was this on, etc etc? the error is pretty explicit, I would inspect the value of your COMSPEC environment variable. fo

Re: [BUGS] BUG #8517: Problem due to libeay32.dll about ordinal

2013-10-10 Thread John R Pierce
On 10/10/2013 6:27 AM, s.mech...@gmail.com wrote: I'm trying since yesterday to install a software which needs to install postgreSQL 8.4 aswell. When the installation is finished, a message appears a few times which says "The 3873 ordinal can't be find in the LIBEAY32.dll dynamic library" (in fre

[BUGS] error

2013-10-10 Thread Andrius Di
Hello, how to solve this error (please see attachment)? Regards, AnDi <> -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8517: Problem due to libeay32.dll about ordinal

2013-10-10 Thread s . mechaab
The following bug has been logged on the website: Bug reference: 8517 Logged by: Sémy Email address: s.mech...@gmail.com PostgreSQL version: 8.4.0 Operating system: Windows 7 - 32bits Description: Hello, I'm trying since yesterday to install a software which needs t

[BUGS] Bit String expand bug

2013-10-10 Thread Gabriel Ciubotaru
Hello, There's a problem with expanding Bit String data types, it make right padding with 0 instead of left padding , making the bit mask almost useless. There is an workaround for that, like mask::bit(n) >> (n-length(mask)), but is much slower than directly left padding on expand.

[BUGS] BUG #8516: Calling VOLATILE from STABLE function

2013-10-10 Thread dwayne
The following bug has been logged on the website: Bug reference: 8516 Logged by: Dwayne Towell Email address: dwa...@docketnavigator.com PostgreSQL version: 9.2.4 Operating system: CentOS Description: Why doesn't PostgreSQL give a warning when calling a volatile funct

Re: [BUGS] BUG #8467: Slightly confusing pgcrypto example in docs

2013-10-10 Thread Peter Eisentraut
The changes shown below are incorrect, I think. On 10/2/13 12:00 PM, Bruce Momjian wrote: > *** gen_salt(type text [, iter_count integer > *** 353,359 > 12 years > > > !md5 > 2345086 > 1 day > 3 years > --- 358,364 ---