Am Dienstag, 17. August 2004 14:26 schrieb Fabien COELHO:
> The patch adds missing the "libpgport.a" file to the installation under
> "install-all-headers". It is needed by some contribs. I install the
> library in "pkglibdir", but I was wondering whether it should be "libdir"?
Yes it should. Ple
> Am Dienstag, 17. August 2004 14:26 schrieb Fabien COELHO:
> > The patch adds missing the "libpgport.a" file to the installation under
> > "install-all-headers". It is needed by some contribs. I install the
> > library in "pkglibdir", but I was wondering whether it should be "libdir"?
>
> Yes it
The following bug has been logged online:
Bug reference: 1228
Logged by: mike
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.3
Operating system: FC3
Description:numeric field from a view from a view does not recognise
any where values
Details:
I hav
The following bug has been logged online:
Bug reference: 1229
Logged by: Andreas Heiduk
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.3
Operating system: Linux Debian testing (i86)
Description:memory leak in backend with COPY and FOREIGN KEY
Details:
On Tue, 24 Aug 2004, PostgreSQL Bugs List wrote:
> I'm trying to COPY ~18Mrows into a table which has a foreign key to another
> table. Memory and swap are exhausted and finaly the postgres.log says:
This is very possibly the space taken up by the trigger queue (which
cannot currently spill out
Different memory usage 7.4.3 vs 8.0.0beta1
client does:
begin
bulk inserts into single table via PQexecParams (1.2 million records)
commit
under 7.4.3 memory usage is static
under 8.0.0beta1 server used increasing memory untill depletion of vm/swap
7.4.3
last pid: 974; load averages: 1.44
After doing some research, this is apparently a
known long-standing issue with inheritance in Postgres. Nobody calls it a
"bug" outright, though. Just a limitation. It makes me wonder how
others have tackled problems of a similar nature.
I've since devised a different way
(http://archives.
BEGIN;
...
...
...
END;
PANIC: invalid xlog record length 236052
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>
--
While performing Load testing using DOTS
http://ltp.sourceforge.net/dotshowto.php ,
during the tests, an update to a specific table starts hanging.
The test name is called BTCJ2
http://ltp.sourceforge.net/dotshowto.php#SEC26,
"This test case mainly uses SQL commands to execute database operatio
Hi, I created a function called "isnull" for test
purposes and when trying to replace it returns the
message belows :
-- Function: public.isnull(anyelement)
-- DROP FUNCTION public.isnull(anyelement);
CREATE OR REPLACE FUNCTION public.isnull(anyelement)
RETURNS bool AS
'
SELECT $1 is null;
dear ladies and gentlemen,
I indicate, that in Vers 8.0 Beta1 / Window
the DLL libecpg.dll is missing. All programs,
being precompiled by ecpg are lacking in that
DLL after being started.
with kind regards G. Abraham
--
Guenter Abraham
I have found a memory leak in the libpq library for postrgesql
7.4.3. The code sample in the attached file will produce the error.
I used Valgrind(http://valgrind.kde.org/)
which is an open source memory profiler application in order to find the
problem.
Machine: Pentium 4
OS: Linux
On Tue, Aug 24, 2004 at 01:33:46PM -0300, PostgreSQL Bugs List wrote:
> CASE
> WHEN to_number(vw_rec_sum.code::text, '999'::text) >
> 194::numeric THEN 3
> WHEN to_number(vw_rec_sum.code::text, '999'::text) <
> 195::numeric AND to_number(vw_rec_sum.code::text, '999'
César Arnold wrote:
> Hi, I created a function called "isnull" for test
> purposes and when trying to replace it returns the
> message belows :
ISNULL is a reserved word. You need to quote the name or pick a
different one.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
[PostgreSQL 8.0beta1 on Windows 2000 Professional]
In case of a leftover postmaster.pid, pg_ctl start
tries to start anyway,
but pg_ctl runservice (as installer by the PostgreSQL
Windows installer) will not start the service, requiring a manual
removal of postmaster.pid.
Apparently no proper erro
I haven't tested this with mingw or MSVC but the default cygwin layout
needs the attached header changes.
pending problems:
src/timezone has a configure problem
pgtz.c:105:2: #error No way to determine TZ? Can this happen?
PGAC_VAR_INT_TIMEZONE return no for cygwin, but our time.h has this:
ext
On Sat, 2004-08-21 at 12:44, Marian Lojka wrote:
> After doing some research, this is apparently a known long-standing
> issue with inheritance in Postgres. Nobody calls it a "bug" outright,
> though. Just a limitation. It makes me wonder how others have tackled
> problems of a similar nature.
> C
=?UTF-8?Q?=E5=A7=9C?= =?UTF-8?Q?=E7=BB=B4?= <[EMAIL PROTECTED]> writes:
> BEGIN;
> ...
> ...
> ...
> END;
> PANIC: invalid xlog record length 236052
> server closed the connection unexpectedly
This is quite unhelpful, if you're not going to show us what you did to
cause it.
Zane <[EMAIL PROTECTED]> writes:
> client does:
> begin
> bulk inserts into single table via PQexecParams (1.2 million records)
> commit
Could we see a concrete test case? I really don't have time to guess
about what contributing factors might be involved ...
regards, t
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> César Arnold wrote:
>> Hi, I created a function called "isnull" for test
>> purposes and when trying to replace it returns the
>> message belows :
> ISNULL is a reserved word. You need to quote the name or pick a
> different one.
I think what he's
On Sun, Aug 22, 2004 at 09:39:07AM +0800, ?? wrote:
> BEGIN;
> ...
> ...
> ...
> END;
>
> PANIC: invalid xlog record length 236052
Huh, so what kind of operations did you execute within the transaction?
--
Alvaro Herrera ()
Voy a acabar con todos los humanos / con los humanos yo acabaré
vo
"Spencer Quin" <[EMAIL PROTECTED]> writes:
> I have found a memory leak in the libpq library for postrgesql 7.4.3.
> The code sample in the attached file will produce the error.
The traceback says that the leak is in libresolv, not libpq. I'm not
sure it's really a leak at all --- I'd expect libr
The following bug has been logged online:
Bug reference: 1230
Logged by: jeff putnam
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: linux
Description:mirror problem
Details:
Website problem. nslookup does not seem to know the
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Sun, Aug 22, 2004 at 09:39:07AM +0800, ?? wrote:
>> PANIC: invalid xlog record length 236052
> Huh, so what kind of operations did you execute within the transaction?
I found one possible explanation, though I don't know if it's the
submitter's
Guys,
Beg pardon if this is a repeat:
Summary: \d option on 8.0b1 PSQL not backward compatible
Severity: Annoyance
Affects: 8.0b1 connecting to 7.4.3
Platform: SuSE Linux 8.2
Description: I get:
jwnet_test=# \d elbs_matter
ERROR: column "reltablespace" does not exist
jwnet_test=# \d cases
E
On Tue, Aug 24, 2004 at 06:56:42PM -0700, Josh Berkus wrote:
> Guys,
>
> Beg pardon if this is a repeat:
>
> Summary: \d option on 8.0b1 PSQL not backward compatible
> Severity: Annoyance
> Affects: 8.0b1 connecting to 7.4.3
Apparently this was fixed after beta 1 ... works for me here.
--
Al
On Tue, Aug 24, 2004 at 06:10:40PM -0400, Tom Lane wrote:
> WARNING: out of shared memory
> ERROR: out of shared memory
> HINT: You may need to increase max_locks_per_transaction.
> WARNING: StartAbortedSubTransaction while in START state
> ERROR: current transaction is aborted, commands igno
Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Summary: \d option on 8.0b1 PSQL not backward compatible
> Apparently this was fixed after beta 1 ... works for me here.
Yeah, Greg Mullane fixed that, see
http://archives.postgresql.org/pgsql-committers/2004-08/msg00312.php
People,
Here's another:
Summary: TOAST error on frequently truncated tables
Version: 7.4.2
Severity: Abort
Platform: Red Hat 9.0
When running a script against a reporting database, I'm getting the following:
DBD::Pg::st execute failed: ERROR: expected both swapped tables to have TOAST
tables
Josh Berkus <[EMAIL PROTECTED]> writes:
> DBD::Pg::st execute failed: ERROR: expected both swapped tables to have TOAST
> tables at sql_data_xfer.pl line 120, line 2.
Have you done more to this table than TRUNCATE it?
We recognized relatively recently that ALTER DROP COLUMN could drop the
last
Tom,
> > DBD::Pg::st execute failed: ERROR: expected both swapped tables to have
> > TOAST tables at sql_data_xfer.pl line 120, line 2.
>
> Have you done more to this table than TRUNCATE it?
>
> We recognized relatively recently that ALTER DROP COLUMN could drop the
> last/only variable-width co
Josh Berkus <[EMAIL PROTECTED]> writes:
> Aha! Yes, the problem is that I dropped the last VARCHAR column, not in that
> table but in one that came after it. Any workaround to fix?
Easiest is to add back a useless varchar column ...
regards, tom lane
--
32 matches
Mail list logo
