The following bug has been logged online:
Bug reference: 6081
Logged by: Tom Hodder
Email address: t...@limepepper.co.uk
PostgreSQL version: 8.4
Operating system: Fedora 14 x86_64
Description:trigger CRUD log entries, or documentation not clear
that triggers do not
Hi,
When I run the SQL below, I get an error on the third call to foo() : ERROR:
could not open relation with OID 884693. I'm quite sure this OID belongs to
the TOAST table corresponding to the temporary table created by foo() during
the third call. The fourth call works fine again.
I
Excerpts from Matthijs Bomhoff's message of mié jun 29 07:40:07 -0400 2011:
CREATE OR REPLACE FUNCTION foo(size_ INTEGER) RETURNS TEXT AS $EOF$
DECLARE
acc_ TEXT := '';
cur_rec_ RECORD;
BEGIN
EXECUTE 'CREATE TEMPORARY TABLE foo_tab(blob TEXT NOT NULL)';
-- Construct a string with
The following bug has been logged online:
Bug reference: 6082
Logged by: Steve Haslam
Email address: araq...@googlemail.com
PostgreSQL version: 9.0.4
Operating system: Debian GNU/Linux (amd64)
Description:server segfault - pg_stat_reset_shared(null)
Details:
=
The following bug has been logged online:
Bug reference: 6083
Logged by: Steve Haslam
Email address: araq...@googlemail.com
PostgreSQL version: 9.0.4
Operating system: Debian GNU/Linux (amd64)
Description:psql script line numbers incorrectly count \copy data
Details:
The following bug has been logged online:
Bug reference: 6084
Logged by: Stewart Fritts
Email address: stewart.fri...@gmail.com
PostgreSQL version: 8.4
Operating system: Windows Server 2003
Description:When Updating Tables with Select Into
Details:
First, I love
The following bug has been logged online:
Bug reference: 6085
Logged by: Olivier LEVESQUE
Email address: olevesq...@gmail.com
PostgreSQL version: 9.0.3
Operating system: RHEL 5.4 Linux 2.6.18 x86_64
Description:pg_upgrade fails when unix_socket_directory != /tmp
On Wed, Jun 29, 2011 at 15:31, Steve Haslam araq...@googlemail.com wrote:
The following bug has been logged online:
Bug reference: 6082
Logged by: Steve Haslam
Email address: araq...@googlemail.com
PostgreSQL version: 9.0.4
Operating system: Debian GNU/Linux (amd64)
On Fri, Jun 17, 2011 at 1:34 AM, Praveen spkumarvay...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 6063
Logged by: Praveen
Email address: spkumarvay...@gmail.com
PostgreSQL version: 8.4
Operating system: windows 7
Description:
On Tue, Nov 2, 2010 at 12:17 PM, heasley h...@shrubbery.net wrote:
The following bug has been logged online:
Bug reference: 5741
Logged by: heasley
Email address: h...@shrubbery.net
PostgreSQL version: 8.4
Operating system: solaris
Description: syslog line
On Jun 29, 2011, at 6:03 PM, Alvaro Herrera wrote:
Excerpts from Matthijs Bomhoff's message of mié jun 29 07:40:07 -0400 2011:
CREATE OR REPLACE FUNCTION foo(size_ INTEGER) RETURNS TEXT AS $EOF$
DECLARE
acc_ TEXT := '';
cur_rec_ RECORD;
BEGIN
EXECUTE 'CREATE TEMPORARY TABLE
Excerpts from Matthijs Bomhoff's message of mié jun 29 15:20:49 -0400 2011:
Possibly related: In some earlier attempts at reproducing this, I
actually tried to use length() instead of md5(). It seemed that I
could not get it to trigger with that. Just selecting * triggers it of
course, but
Magnus Hagander mag...@hagander.net writes:
On Wed, Jun 29, 2011 at 15:31, Steve Haslam araq...@googlemail.com wrote:
= select pg_stat_reset_shared(null)
*server segfault*
Thanks for the report - fixed, and will be in next releases.
Seems like the more appropriate fix in HEAD is to mark the
Dean Rasheed dean.a.rash...@gmail.com writes:
2011/6/28 Renat renat.nasy...@itv.ru:
select * from foo where date_to is null and date_to '2011-01-01'
Expected: 0 rows
But: it return 1 row with id=2
The problem seems to be in _bt_preprocess_keys(), which discards the
a 1 predicate in
On 29/06/2011 10:19 PM, Stewart Fritts wrote:
I recently migrated some data from one set of tables to another within a
single schema. I did this by using a select...into query. Everything moved
perfectly. However; I noticed that the sequence for the receiving table did
not increment with the
problem: now we upgrading our operating system as windows 7 with 64 bit.
i am install above software listed above .
problem is that execption is occured when connection open statement is
executed.
There's no evidence this is a bug. Please post a question on the
pgsql-general
The problem was observed on CentOS 5.6 using postgresql 8.4.7 and
Scientific Linux 6.0 also using postgresql 8.4.7.
The problem could not be replicated on openSUSE 11.4 which has postgresql 9.0.3.
With 8.4.7, I ran into an issue trying to explain a VIEW query.
After much effort, I distilled the
17 matches
Mail list logo
