Rafael Barrios wrote:
Richard, thanks for your response.
here is te information you request:
Don't forget to cc: the mailing list.
CREATE TABLE tbarrio (
bar_coddep character varying(2) NOT NULL,
bar_codmun character varying(3) NOT NULL,
bar_codbarrio character varying(3) NOT NULL,
Mahesh Shinde wrote:
Hi I am using Postgres version *PostgreSQL 7.4.5 on
i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 20030222 (Red Hat
Linux 3.2.2-5).* for an multy user desktop application using VB 6.0
as a front end toll.
Mahesh - please post this to the general mailing list, not the b
The following bug has been logged online:
Bug reference: 1819
Logged by: Steve Peterson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows XP SP 2
Description:COPY filename rejects Windows format path
Details:
Running COPY FROM on a
Thanks for your valuable response.
-- Original Message ---
From: Richard Huxton
To: Rafael Barrios <[EMAIL PROTECTED]>, pgsql-bugs@postgresql.org
Sent: Thu, 11 Aug 2005 08:14:13 +0100
Subject: Re: [BUGS] BUG #1816: Insert null values on a null field
> Rafael Barrios wrote:
> > Ri
> >>> Alvaro Herrera <[EMAIL PROTECTED]> 08/10/05 9:03 AM >>>
> On Mon, Aug 01, 2005 at 06:02:30AM +0100, Aaron Harsh wrote:
> > pg_dump: ERROR: unexpected chunk number 0 (expected 1) for toast value
> > ...
> Looks very much like the table was corrupted. Maybe you should try to
> test your RAM a
The table contains ~10 million rows:
# time psql -c "UPDATE xa_url SET url = url;" -U pgsql pareto
ERROR: out of memory
DETAIL: Failed on request of size 32.
0.000u 0.022s 2:41:14.76 0.0% 88+66k 12+0io 19pf+0w
And the server is running:
PostgreSQL 8.0.0 on i386-portbld-freebsd4.10, compil
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> The table contains ~10 million rows:
> # time psql -c "UPDATE xa_url SET url = url;" -U pgsql pareto
> ERROR: out of memory
> DETAIL: Failed on request of size 32.
If you've got any AFTER UPDATE triggers on that table, you could be
running out of
Steve Peterson wrote:
Running COPY FROM on a Windows server; using a Windows-format fully
qualified path with backslashes results in the backslashes being interpreted
as escapes.
Did you escape the backslashes: C:\\Windows\\Path ?
--
Richard Huxton
Archonet Ltd
--
Steve Peterson wrote:
Running COPY FROM on a Windows server; using a Windows-format fully
qualified path with backslashes results in the backslashes being interpreted
as escapes.
Windows APIs are perfectly happy with regular / forward slashes in pathnames,
in fact, I use them everywhere BUT i
On Thu, 11 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
The table contains ~10 million rows:
# time psql -c "UPDATE xa_url SET url = url;" -U pgsql pareto
ERROR: out of memory
DETAIL: Failed on request of size 32.
If you've got any AFTER UPDATE triggers on tha
On Wed, Aug 10, 2005 at 06:07:24PM -0700, Aaron Harsh wrote:
> > >>> Alvaro Herrera <[EMAIL PROTECTED]> 08/10/05 9:03 AM >>>
> > On Mon, Aug 01, 2005 at 06:02:30AM +0100, Aaron Harsh wrote:
> > > pg_dump: ERROR: unexpected chunk number 0 (expected 1) for toast value
> > > ...
> > Looks very much l
On Thu, 11 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Thu, 11 Aug 2005, Tom Lane wrote:
If you've got any AFTER UPDATE triggers on that table, you could be
running out of memory for the pending-triggers list.
Nope, only have a BEFORE UPDATE, or would that be
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Thu, 11 Aug 2005, Tom Lane wrote:
>> An out-of-memory error should result in a long report in the postmaster
>> log about how many bytes in each memory context --- can you post that?
> This is all I'm seeing in the logs:
> # grep "\[653\]" pgsql
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Thu, 11 Aug 2005, Tom Lane wrote:
>> If you've got any AFTER UPDATE triggers on that table, you could be
>> running out of memory for the pending-triggers list.
> Nope, only have a BEFORE UPDATE, or would that be similar except for at
> which po
I'm running a fairly recent CVS head server, but I think this bug
applies in all versions.
talluria=# delete from items;
ERROR: insert or update on table "players" violates foreign key constraint
"players_accessory1_fkey"
DETAIL: Key (accessory1)=(90205) is not present in table "items".
CONTEXT
On Thu, 11 Aug 2005, Allan Wang wrote:
> I'm running a fairly recent CVS head server, but I think this bug
> applies in all versions.
It doesn't happen for me in 7.4.2 with the example below, although my
couple month old CVS server and an 8.0.x server do error. My first guess
is that there's som
On Thu, 11 Aug 2005, Marc G. Fournier wrote:
On Thu, 11 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Thu, 11 Aug 2005, Tom Lane wrote:
If you've got any AFTER UPDATE triggers on that table, you could be
running out of memory for the pending-triggers list.
No
Just as a reminder, this is an 8.0.0 install, so if you think this might
have been fixed in later sub-releases, plesae let me know and I'll
upgrade/test again ...
On Thu, 11 Aug 2005, Marc G. Fournier wrote:
On Thu, 11 Aug 2005, Marc G. Fournier wrote:
On Thu, 11 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> 'k, does this help any?
> TopMemoryContext: 40960 total in 4 blocks; 8632 free (10 chunks); 32328 used
> SPI Plan: 3072 total in 2 blocks; 1728 free (0 chunks); 1344 used
> TopTransactionContext: 534765568 total in 74 blocks; 2144 free (68 chunks);
On Thu, 11 Aug 2005, Stephan Szabo wrote:
> On Thu, 11 Aug 2005, Allan Wang wrote:
>
> > I'm running a fairly recent CVS head server, but I think this bug
> > applies in all versions.
>
> It doesn't happen for me in 7.4.2 with the example below, although my
> couple month old CVS server and an 8.
On Thu, 11 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
'k, does this help any?
TopMemoryContext: 40960 total in 4 blocks; 8632 free (10 chunks); 32328 used
SPI Plan: 3072 total in 2 blocks; 1728 free (0 chunks); 1344 used
TopTransactionContext: 534765568 total in
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Thu, 11 Aug 2005, Tom Lane wrote:
>> Are you *sure* there are no AFTER triggers here?
>> (Don't forget foreign-key checking triggers.)
> This is all of them ... nothing AFTER, just ON or BEFORE ...
> Foreign-key constraints:
> "xa_classific
22 matches
Mail list logo
