On 07/01/2015 01:13 PM, shibly wrote:
Hi,
We have configured PostgreSQL cluster with repmgr 3.0.1 and PgPool2 3.2 on
Ubuntu 14.04. Now we are getting the following error messages in the log
file.
ERROR: duplicate key value violates unique constraint "pk_os_currentstep"
ERROR: cached plan must
Hi,
We have configured PostgreSQL cluster with repmgr 3.0.1 and PgPool2 3.2 on
Ubuntu 14.04. Now we are getting the following error messages in the log
file.
ERROR: duplicate key value violates unique constraint "pk_os_currentstep"
ERROR: cached plan must not change result type
Any suggestion
Craig Ringer writes:
> On 06/25/2012 04:21 PM, Stefan Schwarzer wrote:
>> When I type in:
>>
>> sudo -u _postgres /usr/local/pgsql-9.1/bin/postgres -D
>> /usr/local/pgsql-9.1/data
>>
>> it spits out:
>>
>> LOG: 0: could not identify current directory: Permission denied
> It's trying to g
On 06/25/2012 04:21 PM, Stefan Schwarzer wrote:
I just went back to the postgres documentation [1] (actually reading all google
results on the error message one after the other) and tried out what was said
there (adapted to my conditions):
sudo -u _postgres /usr/local/pgsql-9.1/bin/postgres -D
> I just went back to the postgres documentation [1] (actually reading all
> google results on the error message one after the other) and tried out what
> was said there (adapted to my conditions):
>
> sudo -u _postgres /usr/local/pgsql-9.1/bin/postgres -D
> /usr/local/pgsql-9.1/data
>
> and s
On 06/25/2012 02:50 PM, Stefan Schwarzer wrote:
> Craig Ringer wrote:
I'm puzzled about why you don't appear to be looking at the server error logs
(/usr/local/pgsql-9.1/data/pg_log) during troubleshooting. They're your main
source of info.
Hmm, I guess it's because I didn't think of it, I wa
>>> sudo su - _postgres /usr/local/pgsql-9.1/bin/initdb -U postgres -D
>>> /usr/local/pgsql-9.1/data --encoding=UTF8 --locale=en_US
>>> sudo su - _postgres /usr/local/pgsql-9.1/bin/pg_ctl start -D
>>> /usr/local/pgsql-9.1/data
>>>
>>> Although I don't get an error message, I don't have the feeli
On 06/22/2012 03:19 PM, Stefan Schwarzer wrote:
sudo su - _postgres /usr/local/pgsql-9.1/bin/initdb -U postgres -D
/usr/local/pgsql-9.1/data --encoding=UTF8 --locale=en_US
sudo su - _postgres /usr/local/pgsql-9.1/bin/pg_ctl start -D
/usr/local/pgsql-9.1/data
Although I don't get an error messa
> sudo su - _postgres /usr/local/pgsql-9.1/bin/initdb -U postgres -D
> /usr/local/pgsql-9.1/data --encoding=UTF8 --locale=en_US
> sudo su - _postgres /usr/local/pgsql-9.1/bin/pg_ctl start -D
> /usr/local/pgsql-9.1/data
>
> Although I don't get an error message, I don't have the feeling that it
>>
>> When I do: sudo launchctl load
>> /Library/LaunchDaemons/org.postgresql.postgres.plist
>> it says: org.postgresql.postgres: Already loaded
>>
>> When I do: /usr/local/pgsql-9.1/bin/initdb -U postgres -D
>> /usr/local/pgsql-9.1/data --encoding=UTF8 --locale=en_US
>> it s
On 06/20/2012 10:40 PM, Stefan Schwarzer wrote:
I need unfortunately to come back to this issue. I (again) re-installed Lion
from scratch, and finally got everything working. The Postgres was running, I
uploaded a couple of dumped SQL files. And then re-started the machine for
another reason
>> I need unfortunately to come back to this issue. I (again) re-installed Lion
>> from scratch, and finally got everything working. The Postgres was running,
>> I uploaded a couple of dumped SQL files. And then re-started the machine for
>> another reason. And suddenly it says again the it can
On 06/19/2012 01:32 AM, Stefan Schwarzer wrote:
I need unfortunately to come back to this issue. I (again) re-installed Lion
from scratch, and finally got everything working. The Postgres was running, I
uploaded a couple of dumped SQL files. And then re-started the machine for
another reason
>>> I guess this is a typical user error. I searched around to find the
>>> solution, but in vain.
>>>
>>> I just upgraded to Lion, and used Kyngchaos libraries for installation of
>>> Postgres.
>>>
>>> Try to get running postgres, and I get this:
>>>
>>> /usr/local/pgsql-9.1/bin/psql -U
On 06/14/2012 06:48 AM, Stefan Schwarzer wrote:
>
>>> Hi there,
>>>
>>> I guess this is a typical user error. I searched around to find the
>>> solution, but in vain.
>>>
>>> I just upgraded to Lion, and used Kyngchaos libraries for installation of
>>> Postgres.
>>>
>>> Try to get running postgr
>> Hi there,
>>
>> I guess this is a typical user error. I searched around to find the
>> solution, but in vain.
>>
>> I just upgraded to Lion, and used Kyngchaos libraries for installation of
>> Postgres.
>>
>> Try to get running postgres, and I get this:
>>
>> /usr/local/pgsql-9.1/bi
On 06/14/2012 06:30 AM, Stefan Schwarzer wrote:
Hi there,
I guess this is a typical user error. I searched around to find the solution,
but in vain.
I just upgraded to Lion, and used Kyngchaos libraries for installation of
Postgres.
Try to get running postgres, and I get this:
/usr/l
Hi there,
I guess this is a typical user error. I searched around to find the solution,
but in vain.
I just upgraded to Lion, and used Kyngchaos libraries for installation of
Postgres.
Try to get running postgres, and I get this:
/usr/local/pgsql-9.1/bin/psql -U postgres
psql: co
On 10/01/2009 07:00 PM, Ounce Snow wrote:
Hi,
this may be a FAQ but I did not see it listed there:
when I run the install (Intel Mac) I get a popup saying
problem running post install step
Installation may not complete correctly
The database cluster initialisation failed
Check the logs(/tmp/in
Hi,
this may be a FAQ but I did not see it listed there:
when I run the install (Intel Mac) I get a popup saying
problem running post install step
Installation may not complete correctly
The database cluster initialisation failed
what have I missed please?
Greg
I don't know: I'm not subscribed to the anno9unce list so I was not
aware 8.4 has now a production release.
In the past upgrading from 8.2 to 8.3 solved a big issues but at the
time the application is not in production.
So we are going to evaluate this option.
Anyway after reading the manual in th
Ivano Luberti writes:
> My problem is I know what query has failed , but I don't know the other
> one that caused the deadlock condition.
Ah. Is it practical for you to upgrade to PG 8.4? IIRC the deadlock
reporting code got improved in 8.4 to log all the queries involved.
Tom, thanks for your answer: the reason I failed to find
AccessExclusiveLock
is beacuse that string of character is never written in the manual while
AccessShareLock
is written as it is written above in the manual in the section about index
lockin.
Not knowing the manual in detail I didn't
Ivano Luberti writes:
> I'm trying to understand why I can have this kind or error (it is
> probably some programming mistake) but reading the PostgresSQL manual I
> cannot find any trace of AccessExclusiveLock , while I have found
> explanation of what AccessShareLock is.
> First question: is th
Hi all, I use PostgresSQL 8.3 through JDBC
Recently one transaction has failed with the following error message:
Detail: Process 10660 waits for AccessShareLock on relation 36036 of
database 34187; blocked by process 2212.
Process 2212 waits for AccessExclusiveLock on relation 36044 of database
34
I am getting an error trying to connect to PostgreSQL db using Visual
Basic.NET 2005. The error message is "FATAL: invalid command-line
arguments for server process. HINT: Try "postgres --help" for more
information."
Here is a the snippet of code to create connection. Looking for
suggestions
"Anthony Brock (KG4AGD)" <[EMAIL PROTECTED]> writes:
> I am getting an error trying to connect to PostgreSQL db using Visual
> Basic.NET 2005. The error message is "FATAL: invalid command-line
> arguments for server process. HINT: Try "postgres --help" for more
> information."
This implies inco
I am getting an error trying to connect to PostgreSQL db using Visual
Basic.NET 2005. The error message is "FATAL: invalid command-line
arguments for server process. HINT: Try "postgres --help" for more
information."
Here is a the snippet of code to create connection. Looking for
suggestions
"Brian J. Erickson" <[EMAIL PROTECTED]> writes:
> I get the following message in the "pgstartup.log":
> postmaster cannot access the server configuration file
> "/database/postgresql.conf": Permission denied
Are you trying to change the standard config file location on a
Red Hat or Fedora system?
Hello,
I get the following message in the "pgstartup.log":
postmaster cannot access the server configuration file
"/database/postgresql.conf": Permission denied
I have:
1) read the file doing the following:
a) su posgres
b) less postgresql.conf
2) made sure each directory to file is read
> If I click on a link while on the
> http://techdocs.postgresql.org/ site, for example, under
> "Quick Reference Material", "PostgreSQL Notes", I briefly
> see an error message that says: "Notice: Use of undefined
> constant userid
> - assumed 'userid' in
> /usr/local/www/techdocs.postgresql
If I click on a link while on the http://techdocs.postgresql.org/ site, for
example, under "Quick Reference Material", "PostgreSQL Notes", I briefly
see an error message that says: "Notice: Use of undefined constant userid
- assumed 'userid' in
/usr/local/www/techdocs.postgresql.org/technotes/re
On Wed, Oct 26, 2005 at 07:47:51PM -0700, Bob Pawley wrote:
> I have a base table called "process". Each row of this table is anchored by
> a serial column labeled "fluid_id".
What do you mean by "anchored by"? Is fluid_id the primary key for
process? Or is fluid_id a foreign key reference to s
ing however, I hope
this explanation is somewhat clear.
Thanks for your help.
Bob
- Original Message -
From: "Michael Fuhr" <[EMAIL PROTECTED]>
To: "Terry Lee Tucker" <[EMAIL PROTECTED]>
Cc: "Postgre General"
Sent: Wednesday, October 26, 2
On Wed, Oct 26, 2005 at 07:00:06PM -0600, Michael Fuhr wrote:
> You *can* pass arguments to trigger functions but it's done a little
> differently than with non-trigger functions. The function must be
> defined to take no arguments; it reads the arguments from a context
> structure instead of in t
On Wed, Oct 26, 2005 at 07:45:19PM -0400, Terry Lee Tucker wrote:
> You cannot pass argments to trigger functions. You can to other types of
> functions, but not functions used as triggers. Arguments are passed regarding
> the old and new records and other built in variables regarding what kind o
Bob Pawley <[EMAIL PROTECTED]> writes:
> I'm not sure what you mean.
>
> base(int4) is the name of the function that I want to call. It follows
> the format of an example in a Postgresql book I use (or perhaps
> misuse).
>
> Are you saying that I need to redo the function???
You need to make it a
IL PROTECTED]>
> To: "Bob Pawley" <[EMAIL PROTECTED]>
> Cc: "Postgre General"
> Sent: Wednesday, October 26, 2005 2:23 PM
> Subject: Re: [GENERAL] Error Message
>
> > Bob Pawley <[EMAIL PROTECTED]> writes:
> >> The function name is list
t;[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Postgre General"
Sent: Wednesday, October 26, 2005 2:23 PM
Subject: Re: [GENERAL] Error Message
Bob Pawley <[EMAIL PROTECTED]> writes:
The function name is listed under Functions as - base(int4)
Bob Pawley <[EMAIL PROTECTED]> writes:
> The function name is listed under Functions as - base(int4)
Trigger functions cannot take any explicit parameters.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to in
I am attempting to create a new trigger through the "new Trigger" interface
on version 8 installed on Windows.
The following is the sql that the interface generates
CREATE TRIGGER trig1 AFTER INSERT ON process FOR EACH
ROW EXECUTE PROCEDURE base(int4);COMMENT ON TRIGGER trig1 ON
proce
Hi All,
false alarm... I found the problem. I tried to reuse an
insertStatement. can't do it.
Phil
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Hi All,
I'm getting the following from an "insertStatement.executeUpdate();"
error message:
postgresql.stat.result
[EMAIL PROTECTED]
Does anybody know why?
thanks,
Phil
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an
On Wed, 1 Sep 2004 12:53 pm, Daniel Secomb wrote:
> Hi,
>
> I'm using PostgreSQL 7.3.4 with phpPgAdmin 2.4.2 and the ".sql" file I'm
> trying to import came from a dump from a server running PostgreSQL 7.0.3.
>
I'd suggest a phpPgAdmin upgrade 3.4 is the latest.
> I just got this error message t
Hi,
I'm using PostgreSQL 7.3.4 with phpPgAdmin 2.4.2 and the ".sql" file I'm
trying to import came from a dump from a server running PostgreSQL 7.0.3.
I just got this error message trying to import the PostgreSQL
database file into phpPgAdmin. The error message was as
follows:
Error
-
On 3 Mar 2004, Eric wrote:
> Hello.
>
> After I have performed several queries by an external program on the
> database, an error message appeared:
> "hard limit on result handles reached is not a valid query result"
>
> May I know how to solve the problem?
Sounds like an application issue, not
Hello.
After I have performed several queries by an external program on the
database, an error message appeared:
"hard limit on result handles reached is not a valid query result"
May I know how to solve the problem?
Thank you
---(end of broadcast)
At 01:40 PM 8/6/2003, Peter Eisentraut wrote:
You need to double-quote the names or they will be converted to lower
case.
Thank you both. The reason why the initial table creation have quoted
columns names is that it's generated by a program we use for schema
creation. I'm currently adding to it
On Wed, Aug 06, 2003 at 03:06:12PM +0100, Jan Oksfeldt Jonasen wrote:
> At 01:40 PM 8/6/2003, Peter Eisentraut wrote:
> >You need to double-quote the names or they will be converted to lower
> >case.
> >
>
> Thank you both. The reason why the initial table creation have quoted
> columns names is
On 6 Aug 2003 at 14:34, Jan Oksfeldt Jonasen wrote:
> Hi,
> I'm a very new user of the PostgreSQL database, but I've quickly
> encountered what I consider an pretty odd error. Let it be said, this is
> using the PeerDirect PostgreSQL Beta 4 using Win2K SP3, so it's bound to
> have certain issue
W. van den Akker writes:
> I'am using PostgreSQL for a project. The users of the programs aren't
> happy with the English-messages returned from 'PQerrorMessage'. Is it
> possible to create and load a localized message file, so that
> errormessage can be shown to the users in their own language?
Can anyone tell me what the following two messages mean? They are
from 6.5.3.
thanks,
--titus
NOTICE: equal: don't know whether nodes of type 719 are equal
NOTICE: LockReleaseAll: xid loop detected, giving up
--
Titus Brown, [EMAIL PROTECTED]
"Jackson, Kevin J." wrote:
>
> 1) What does the following mean:
> PostgresSQL query failed: ERROR: Bad date external representation
You might have an illegal date string format, though this kind of
message also shows up in other circumstances IIRC.
Try 'MM/DD/' or '-MM-DD'...
> 2) Is
Make sure your perl DBD-Pg and DBI are compiled with the correct version
of postgres.
> Erik Colson wrote:
>
> Hi!
>
> I installed (compiled) latest versions of Perl, Postgres.
>
> I can access the database via 'psql' but allways get an error when
> trying to connect from a perl-script :
>
>
54 matches
Mail list logo
