Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Meetesh Karia wrote:
>> After upgrading to 8.3 and Slony 1.2.13, one of our import processes
>> started constantly failing because of deadlock. Our import process
>> (pl/pgsql function) just uses COPY FROM to populate a temp table and
>> then inse
Meetesh Karia wrote:
> Hi all,
>
> After upgrading to 8.3 and Slony 1.2.13, one of our import processes
> started constantly failing because of deadlock. Our import process
> (pl/pgsql function) just uses COPY FROM to populate a temp table and
> then inserts from that (without any special lo
Stefan Kaltenbrunner wrote:
[EMAIL PROTECTED] wrote:
I have just installed Postgres 8.3.1.
And /usr/local/etc/rc.d/postgresql and
/contrib/start-scripts/freebsd scripts are different
BUG in installator?
the one in /usr/local/etc/rc.d/postgresql is likely the on that freebsd
supplies if you
Hi all,
After upgrading to 8.3 and Slony 1.2.13, one of our import processes
started constantly failing because of deadlock. Our import process
(pl/pgsql function) just uses COPY FROM to populate a temp table and
then inserts from that (without any special locks, etc). And, the
deadlock err
[EMAIL PROTECTED] wrote:
I have just installed Postgres 8.3.1.
And /usr/local/etc/rc.d/postgresql and
/contrib/start-scripts/freebsd scripts are different
BUG in installator?
the one in /usr/local/etc/rc.d/postgresql is likely the on that freebsd
supplies if you install from the porttree so
I have just installed Postgres 8.3.1.
And /usr/local/etc/rc.d/postgresql and /contrib/start-scripts/freebsd
scripts are different
BUG in installator?
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Eugen Konkov" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, April 22, 2008 6:1
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> yamaguti=# select distinct max(j) from t1;
>> ERROR: could not find pathkey item to sort
> For the benefit of anyone searching the archives for the problem we
> just hit, this message also occurs in 8.3.1 and also occurs against
> the above test ta
On Tue, 22 Apr 2008, Amit Mujawar wrote:
The following bug has been logged online:
Bug reference: 4123
PostgreSQL version: 8.1
Description:Statement.setQueryTimeout does not work with Postgres
Java Driver
Details:
I am using PostgreSQL through JDBC
PostgreSQL ??? 8.1, Driver -
>>> On Wed, Mar 26, 2008 at 9:23 PM, in message
<[EMAIL PROTECTED]>, Taiki Yamaguchi
<[EMAIL PROTECTED]> wrote:
> 8.3.0
> ==
> yamaguti=# create table t1 (i int, j int primary key);
> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
> "t1_pkey" for tabl
"Eugen Konkov" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: 8.3.1
> Operating system: FreeBSD 6.3
> Description:./postres 'restart' does not start server with same
> options as 'start' does
You'd need to take that up with whoever supplied your startup script.
The one we provide (in
Yikes! I already done a reindexing of the table as there where locks that were
holding back some jobs that needed to finished. But in case the problem should
appear again we will take a copy of the actual data file.
Anyway, the case must regarded as solved. Put shortly, reindex the table/index.
John Parnefjord wrote:
> > Please copy out the files as requested in that email - I'm sure Tom
> > is still interested in debugging it to find the issue. After that,
> > try a REINDEX to see if it solves your problem.
>
> Ok, see the snippets below. I just cut them from the PgAdminIII
> interface.
> Please copy out the files as requested in that email - I'm sure Tom is
> still interested in debugging it to find the issue. After that, try a
> REINDEX to see if it solves your problem.
Ok, see the snippets below. I just cut them from the PgAdminIII interface. Drop
me a mail if you need more i
The following bug has been logged online:
Bug reference: 4123
Logged by: Amit Mujawar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP
Description:Statement.setQueryTimeout does not work with Postgres
Java Driver
Details:
I am us
The following bug has been logged online:
Bug reference: 4122
Logged by: Eugen Konkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: FreeBSD 6.3
Description:./postres 'restart' does not start server with same
options as 'start' does
Detai
John Parnefjord wrote:
> Hi!
>
> Hope anyone can shed some light on this. I was struck by the
> following error in the slony log but I believe it's not a slony
> error, rather that slony triggers an error in PostgreSQL. The error
> message is:
Correct, that's not a backend error.
> cleanupThrea
Try to look into base/16403/ directory and check if file 469917 exists. And run
select relname from pg_class where relfilenode=469917
to determine which relation (table) is affected.
Zdenek
PS: 8.1 version of PostgreSQL is not supported on win. Use 8.3
Boldinov napsal(a):
Hi!
Hope anyone can shed some light on this. I was struck by the following error in
the slony log but I believe it's not a slony error, rather that slony triggers
an error in PostgreSQL. The error message is:
cleanupThread: vacuum analyze sl_seqlog; - ERROR: failed to re-find parent
key in "
The following bug has been logged online:
Bug reference: 4121
Logged by: Boldinov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Windows Server 2003 Standart
Description:ERROR: could not open relation 1663/16403/469917:
Invalid argument
19 matches
Mail list logo
