The following bug has been logged on the website:
Bug reference: 8469
Logged by: Dennis
Email address: dennis.noord...@helsinki.fi
PostgreSQL version: 9.3.0
Operating system: FreeBSD 9.2-RC4
Description:
Hi,
After upgrading an 8.1 version to 9.3.0 I am suddenly
The following bug has been logged on the website:
Bug reference: 8126
Logged by: dennis coomans
Email address: dennis.coom...@hva.nl
PostgreSQL version: 8.4.17
Operating system: Win7
Description:
in PgAdmin menu Tools is translated
%Gereedschappen
The '%&#x
The following bug has been logged online:
Bug reference: 6086
Logged by: Dennis
Email address: dennis.noord...@helsinki.fi
PostgreSQL version: 9.0.4
Operating system: FreeBSD 8.2 (64 bit)
Description:Segmentation fault
Details:
For some reason a 9.0.4 server which
:1928
#54 0x005a4810 in ServerLoop () at postmaster.c:3447
#55 0x005a619d in PostmasterMain (argc=3, argv=0x9b0540) at
postmaster.c:1040
#56 0x00552a5e in main (argc=3, argv=0x9b0540) at main.c:188
We are running 8.4.2 on this setup; we tried running the setup with
8.4.3 t
dvisory_lock_shared(12345)", the result was
the same as when it was run on the same machine, which was a "false"
return.
Thanks for your help and clarifying this for us.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Saturday, September 05, 2009 6:02 PM
To
The following bug has been logged online:
Bug reference: 5036
Logged by: Dennis Seran
Email address: dse...@novonics.com
PostgreSQL version: 8.4
Operating system: Windows XP and RHEL
Description:Advisory locks have unexpected behavior
Details:
Here is the scenario
The following bug has been logged online:
Bug reference: 4814
Logged by: Dennis Noordsij
Email address: dennis.noord...@helsinki.fi
PostgreSQL version: 8.4 SNAP 17MAY
Operating system: Linux
Description:Segmentation fault when using indexed prefix FT search
Details
On Tuesday 05 May 2009 17:16:03 Tom Lane wrote:
> "Dennis Noordsij" writes:
> > (gdb) bt
> > #0 0x004eecf7 in compute_scalar_stats (stats=0x1abd878,
> > fetchfunc=0x4f0f30 , samplerows= > out>, totalrows=4154315)
> > at analyze.c:232
The following bug has been logged online:
Bug reference: 4793
Logged by: Dennis Noordsij
Email address: dennis.noord...@helsinki.fi
PostgreSQL version: snapshot/beta1
Operating system: 64bit arch Linux
Description:Segmentation fault when doing vacuum analyze
Details
gcc guys in a bug report.
Dennis
On Friday 23 May 2008, Gregory Stark wrote:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
> > IMHO, what you have here is a compiler bug, or at least the gcc boys are
> > going to need to provide a damn good excuse why it's not.
&
The following bug has been logged online:
Bug reference: 4190
Logged by: Dennis Gilmore
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Linux
Description:sparc64 test suite fails
Details:
errors test fails. the following is the output
The following bug has been logged online:
Bug reference: 2751
Logged by: Dennis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Gentoo 2006.1 server x86
Description:contrib\pgxml.sql
Details:
contrib\pgxml.sql has reference to
t's broken imho.
Having a statement in the doc saying "please don't do this because you
will corrupt the data" doesn't really make the situation better.
/Dennis
---(end of broadcast)---
TIP 6: explain analyze is your friend
Package: postgresql-8.0
Version: 8.0.3-13
Severity: important
Tags: patch, upstream
Here's the problem:
db=# CREATE GROUP g1;
CREATE GROUP
db=# CREATE USER u1 IN GROUP g1;(1)
CREATE USER
# cat /var/lib/postgresql/8.0/main/global/pg_group
#
The file gets rewritten, but th
ng
function there? Ie, is it really a feature?
--
/Dennis Björklund
---(end of broadcast)---
TIP 8: explain analyze is your friend
ON bar(int, int)
RETURNS setof int
AS 'SELECT $1 UNION ALL SELECT $2;'
LANGUAGE sql;
So it seems that it's not just the type that decide how the function can
be used, it's also the language the function is defined in.
Bug?
--
/Dennis Björklund
The following bug has been logged online:
Bug reference: 1626
Logged by: Dennis Vshivkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6, 8.0.2
Operating system: Debian GNU/Linux sarge, kernel 2.4.x
Description:Minimum documented values aren't accepte
On Sat, Apr 23, 2005 at 01:58:13AM -0400, Tom Lane wrote:
>> Time zone component should be added, not subtracted.
> Why?
Here's three different ways of looking at the question and
seeing that what Postgres is currently doing must be wrong.
Correcting the way time zone component is applied fixe
The following bug has been logged online:
Bug reference: 1618
Logged by: Dennis Vshivkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6, 8.0.1
Operating system: Debian GNU/Linux, kernel 2.4
Description:EXTRACTing EPOCH from TIME WITH TIME ZONE is broken
The following bug has been logged online:
Bug reference: 1617
Logged by: Dennis Vshivkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6, 8.0.1
Operating system: Debian GNU/Linux, kernel 2.4
Description:TIME WITH TIME ZONE comparison is partially broken
The following bug has been logged online:
Bug reference: 1556
Logged by: Dennis van Dok
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.4
Operating system: Debian GNU/Linux 3.0
Description:psql ON_ERROR_STOP returns 3 when scripts ends in C
style comment
The following bug has been logged online:
Bug reference: 1524
Logged by: Dennis van Dok
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.4
Operating system: Linux
Description:drop view cascade deletes other user's views
Details:
Using DROP VIEW or
Name: Dennis
Huebner
Email: [EMAIL PROTECTED]
PostgreSQL
version: 8.0
Operation
system: Windows
XP Professional
Short
description: No connection to Server
Hi
there,
I
have trouble with newer versions of postgresql
How come this work in pg (8.0 and older):
CREATE TABLE bug (x int);
SELECT count(bug) FROM bug;
Shouldn't it complain and say that "bug" is not a column?
--
/Dennis Björklund
---(end of broadcast)---
TIP 5: Have you checke
Name: Dennis
Hübner
Email: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operation system: Windows XP Professional
Short description: No connection to Server
Hi there,
I have trouble with newer
versions
The following bug has been logged online:
Bug reference: 1442
Logged by: Dennis Hübner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP Professional
Description:No connection to Server
Details:
Hi there,
I have trouble with
gested to not perform step 3. Instead one need to do that
when the default value is used.
--
/Dennis Björklund
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
n #2?
One could even save the string as it was before parsning if one wants to
(could make it easier to edit in a graphical client like pgadmin3).
--
/Dennis Björklund
---(end of broadcast)---
TIP 8: explain analyze is your friend
ay the smallest int type that fits it (when it is
an integer).
If one have a default value like '2' it would get the type text but that
would still work even if the column is a int column, wouldn't it?
I assume here that we must give the default value a real type. Values of
type u
it's documented
it's not a bug (per definition).
--
/Dennis Björklund
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
e an array
was not allowed. Now I know that you are allowed to form such an
expression and that it evaluates to the NULL array. The documentation
should be fixed then (or maybe it is documented buy i've not seen it).
--
/Dennis Björklund
---(end of broadcast)-
On Thu, 15 Jan 2004, Tom Lane wrote:
> > dennis=# INSERT INTO foo VALUES (ARRAY[2,NULL]);
> > INSERT 25353 1
>
> > That last insert contains a NULL value which are not allowed in arrays and
> > yet a insert is performed. The table contains a NULL value afterwards
>
On Thu, 15 Jan 2004, Dennis Bjorklund wrote:
> A person (cross) in the irc channel
Actually, he calls himself crass which is the only name I have :-)
Not very important, but I like things to be correct (when I can).
--
/Dennis Björklund
---(end of broadc
A person (cross) in the irc channel have found a bug with the new arrays.
Here is what I did to reproduce:
dennis=# CREATE TABLE foo (a int[]);
CREATE TABLE
dennis=# INSERT INTO foo VALUES (ARRAY[2,NULL]);
INSERT 25353 1
That last insert contains a NULL value which are not allowed in arrays and
chance that I did :-)
Thanks!
--
/Dennis
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
In current cvs I get
dennis=# CREATE FUNCTION foo () returns int AS 'select a;' language 'sql';
ERROR: column "a" does not exist
ERROR: column "a" does not exist
It should only be one error.
--
/Dennis
---(end of broadcast)
Marek Lewczuk wrote:
Hello,
I think that there is a bug in plPGSQL - or maybe I don't know something
about this language. Try to create this function
Ok., this is the function created in plPGSQL:
CREATE FUNCTION "public"."test" (text, text) RETURNS text AS'
BEGIN
IF $1 THEN
RETURN $1;
ELSE
in pg, and when I first drop
the function, do the load and then create the function again. But it makes
no difference.
I run redhat 9, maybe load works in other dists/operating systems?
--
/Dennis
---(end of broadcast)---
TIP 6: Have you searche
behind the current
behaviour.
It would of course not be difficult to add a definition of + with the
integer first and the date as the second argument. To me it's not much of
an improvement, but it's not for me to decide. The postgresql operator +
is not the same a
the mantra is to always check hardware first. Do a disk and memory check.
Dmitry Tkach wrote:
I am experiencing database server crashes quite frequently (sometimes,
*daily*), and I am having hard time identifying what could possibly be
causing them :-(
They seem to be happenning kinda randomly
Oops :)
We're talking 7.1 rc4 here.
--
Met vriendelijke groet,
Dennis Fleurbaaij <[EMAIL PROTECTED]>
Stichting CORE http://www.core-lan.nl
Tel: +31 (0)6 54 21 53 65
Fax: +31 (0)20 86 47 059
rying to do it right but forgetting how dumb
users are. You obviously catch the SIGPIPE but then gerget to check the
errno. It's a quick fix no doubt.
Load goed to 100% btw.
In anycase let me know what happens,
Cheers,
Dennis Fleurbaaij
[EMAIL PROTECTED]
42 matches
Mail list logo
