On Thu, 12 Nov 2009, artur saldanha wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5182
> Logged by: artur saldanha
> Email address: artur.salda...@gmail.com
> PostgreSQL version: 8.3.5
> Operating system: Fedora 64
> Description:query with de
On Tue, 13 Oct 2009, dan wrote:
> Let's say I have a table t with 5 columns c1 NOT NULL, c2 NOT NULL, c3, c4,
> c5
> and I have a UNIQUE index on (c1, c2) (remember c1 and c2 have a not null
> constraint)
>
> When I run the query:
> select c1,c2 from t
>
> I expect the explain to say index scan; i
On Thu, 5 Feb 2009, Eduard Deacoon wrote:
> For example:
> --- Function convert column to string with delimiter
> --- $1 - TABLE with COLUMN to convert
> --- $2 - COLUMN to convert
> --- $3 - COLUMN for WHERE CLAUSE
> --- $4 - WHERE value
> --- $5 - delimeter
> --- In fact: SELECT $2 FROM $1 WHERE
On Tue, 9 Sep 2008, Kevin wrote:
> The following bug has been logged online:
>
> Bug reference: 4412
> Logged by: Kevin
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.15
> Operating system: Gentoo Linux
> Description:Check constraints cannot be added to
On Wed, 27 Aug 2008, Daryl Joubert wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4380
> Logged by: Daryl Joubert
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3.3
> Operating system: WinXP SP2
> Description:Comparison of OLD and N
On Sun, 30 Mar 2008 [EMAIL PROTECTED] wrote:
> PROBLEM:
> How to FULL JOIN groups=1 from table 'a' with groups=2 from table 'b'
> and exclude original NULL groups not thouse which FULL JOIN produce?
As far as I can tell, all the results you got were exactly what the SQL
spec requires for the que
On Fri, 7 Mar 2008, Tom Lane wrote:
> "Jan Strube" <[EMAIL PROTECTED]> writes:
> > Description:Comparison of user defined domain doesn't work
>
> I can't reproduce this here --- the test case gives the expected output
> on both 8.2 and 8.3. (I'm checking CVS tip not the 8.3.0 release, bu
On Tue, 22 Jan 2008, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > On Tue, 22 Jan 2008, Tom Lane wrote:
> >> Hmm. I wonder why we are bothering with FOR SHARE locks on the
> >> referencing table, when we don't have any intention to chang
On Tue, 22 Jan 2008, Tom Lane wrote:
> hubert depesz lubaczewski <[EMAIL PROTECTED]> writes:
> > apparently revoking update rights on referencing table blocks deletes on
> > master table:
>
> >> revoke update on b from test;
> > REVOKE
>
> >> delete from a where id = 1;
> > ERROR: permission den
On Thu, 16 Aug 2007, Jens Schicke wrote:
> The following bug has been logged online:
>
> Bug reference: 3542
> Logged by: Jens Schicke
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.4
> Operating system: GNU/Linux
> Description:Dropped and recreated colu
On Thu, 26 Jul 2007, [UTF-8] Т�^C�^Gков �^\и�^Eаил wrote:
> Please, help me!
> My code:
> "IF char_length(substring(str from '^[a-zA-Z]*://'))=0 THEN
>str:= 'http://'||str;
> END IF;"
>
> If str= http://www.msn.com then nothing happen
> (all is OK), but if str= just www.msn.com then nothing h
On Tue, 22 May 2007, Max Khon wrote:
> Stephan Szabo wrote:
>
> >>>>> "delete from foo" fails:
> >>>>> ERROR: update or delete on table "bar" violates foreign key constraint
> >>>>> "foobar_fk0" on table &
On Mon, 21 May 2007, Max Khon wrote:
> Stephan Szabo wrote:
> > On Thu, 17 May 2007, Tom Lane wrote:
> >
> >> Max Khon <[EMAIL PROTECTED]> writes:
> >>> "delete from foo" fails:
> >>> ERROR: update or delete on table "bar
On Thu, 17 May 2007, Tom Lane wrote:
> Max Khon <[EMAIL PROTECTED]> writes:
> > "delete from foo" fails:
>
> > ERROR: update or delete on table "bar" violates foreign key constraint
> > "foobar_fk0" on table "foobar"
> > SQL state: 23503
> > Detail: Key (bar_id)=(1) is still referenced from table
On Fri, 4 May 2007, Jose Blanco wrote:
> I'm not sure what you mean by "C" and how do I change this?
It's a locale name. The ordering is effectively byte order ordering,
while many other locales like en_US have more interesting sorting rules.
IIRC, the locale can only be set at initdb time curren
On Fri, 4 May 2007, Jose Blanco wrote:
> This second time I did, see
>
> select author, sort_author from itemsbyauthor where sort_author like 'tan%'
> order by 2;
>
>
> "order by 2"
>
> Or am I not understanding something?
One issue you might not realize is that the sort order for some locales
i
On Tue, 6 Feb 2007, Aaron Logue wrote:
> On Mon, 5 Feb 2007, Stephan Szabo wrote:
> > On Fri, 2 Feb 2007, Aaron Logue wrote:
> > > The following bug has been logged online:
> > >
> > > Bug reference: 2961
> > > Logged by: Aaron Log
On Fri, 2 Feb 2007, Aaron Logue wrote:
> The following bug has been logged online:
>
> Bug reference: 2961
> Logged by: Aaron Logue
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.1
> Operating system: Linux (various flavors)
> Description:NULL values in s
On Mon, 27 Nov 2006, Shawn Tayler wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2788
> Logged by: Shawn Tayler
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.5
> Operating system: Linux 2.6.17
> Description:Create Function operat
On Mon, 21 Aug 2006, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Yeah, I think there are a few possibilities around truncate inside a
> > savepoint that's rolledback that we have to be careful of.
>
> Yuck :-(
>
> > If we could mark t
On Mon, 21 Aug 2006, Tom Lane wrote:
> Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> > CREATE TABLE category (
> > id INT PRIMARY KEY,
> > name TEXT);
>
> > CREATE TABLE category_todo (
> > cat_id INT REFERENCES category(id)
> > DEFERRABLE INITIALLY DEFERRED
> > );
>
>
On Fri, 4 Aug 2006, Luiz Henrique wrote:
> Hi, could you tell me how postgresql look for a referenced key? It looks in
> table index? Maybe only the index is corrupted?
It basically runs a query like:
SELECT * FROM parenttable WHERE keycol1 = ? [AND keycol2 = ? ...] FOR
SHARE
It should act lik
On Wed, 2 Aug 2006, Luiz Henrique wrote:
> Hi,
>
> I'm running Postgresql 7.3 in Debian Woody OS.
>
> After some time working properly, insert's statements related this error:
>
>
> referential integrity violation - key referenced from xxx not found in yyy
>
>
> This error would be norma
On Thu, 27 Jul 2006, Steven Adams wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2553
> Logged by: Steven Adams
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system: Red Hat Linux 3.2.3-42
> Description:Outer join
On Tue, 2 May 2006, James wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2417
> Logged by: James
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Microsoft Windows XP Professional
> Description:bug for finding st
On Fri, 28 Apr 2006, Sidar Lopez Cruz wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2412
> Logged by: Sidar Lopez Cruz
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.3
> Operating system: Ubuntu 6.04
> Description:Foreing key acc
On Thu, 13 Apr 2006, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > On Wed, 12 Apr 2006, Andreas Kretschmer wrote:
> >> i want to add a check constraint like:
> >> create table foo (i char(7) CHECK (i ~ '^[0-9]{6,7}$'));
> >>
On Wed, 12 Apr 2006, Andreas Kretschmer wrote:
> The following bug has been logged online:
>
> Bug reference: 2390
> Logged by: Andreas Kretschmer
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.3
> Operating system: Debian Linux
> Description:check const
On Wed, 5 Apr 2006, Pavel Golub wrote:
> The following bug has been logged online:
>
> Bug reference: 2377
> Logged by: Pavel Golub
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.0
> Operating system: Windows XP
> Description:pg_constraint didnt't updated
On Wed, 22 Mar 2006, Marinos Yannikos wrote:
> Stephan Szabo schrieb:
> > AFAICS, our behavior follows SQL.
> >
> > a NOT IN b is NOT(a IN b)
> > IN is defined in terms of = ANY.
> > a =ANY (b) is basically (by my reading of 8.8 anyway):
> > True if a =
On Fri, 17 Mar 2006, Patrick Narkinsky wrote:
> This may be expected behavior, but it certainly doesn't seem right to me,
> and it works as expected in sqlite.
>
> The database is as follows:
>
> BEGIN TRANSACTION;
> create table a (
> id integer,
> text varchar(20)
> );
> INSERT INTO a VALUES(0,'
On Mon, 13 Mar 2006, TomasKlockar wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2317
> Logged by: TomasKlockar
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.3.2/7.4.7
> Operating system: linux(fedora)
> Description:Wrong sorting o
On Sun, 12 Mar 2006, L.Jumadi wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2314
> Logged by: L.Jumadi
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.3
> Operating system: SimplyMepis 3.4.3 with kernel 2.6.15.2
> Description:The
On Mon, 6 Mar 2006, Reece Hart wrote:
> On Mon, 2006-03-06 at 11:03 +, Alexander Pivovarov wrote:
> > e.g. I have a table "weather".
> > when I run:
> > mydb=# \d "weatheR"
> > Did not find any relation named ""weatheR"".
> >
> > weatheR is double quoted by "" in error message
>
> This is not
On Thu, 2 Mar 2006, Adriaan van Os wrote:
> Tom Lane wrote:
>
> > Adriaan van Os <[EMAIL PROTECTED]> writes:
> >> The manual is simply taking an old prejudice as a fact.
> >
> > No, it is stating a fact as as fact. The existence of one
> > counterexample does not disprove the generalization.
>
>
On Sun, 26 Feb 2006, Dhanaraj wrote:
> I have two tables, let's say A and B.
>
> B is a child of a in one to many relationship. A contains records that are
> not referenced by B.
>
> I am running a query:
>
> select * from A t1 where t1.id not in (select t2.A_id from B t2);
>
> It returns 0 rows.
On Fri, 10 Feb 2006, Sergei Dubov wrote:
> I have two tables, let's say A and B.
>
> B is a child of a in one to many relationship. A contains records that are
> not referenced by B.
>
> I am running a query:
>
> select * from A t1 where t1.id not in (select t2.A_id from B t2);
>
> It returns 0 ro
On Sun, 5 Feb 2006, Martin Pitt wrote:
> Hi PostgreSQL developers!
>
> I recently got the email below and confirmed that I get the same
> broken collation order in de_DE.UTF-8 as the original reporter (who
> probably uses pt_PT.something). It works fine in C, though.
This is probably not "broken
On Fri, 3 Feb 2006, Patrick Rotsaert wrote:
>
> >One question is what does the explain (without analyze) plan look like for
> >the above and are the row estimates valid in the case of one of the hash
> >plans.
> >
> >
> pointspp=# explain select trid, count(*) from pptran group by trid
> having c
On Mon, 30 Jan 2006, Patrick Rotsaert wrote:
> Problem:
> ---
> Executing a select query causes the backend to crash. This is the output
> from the psql frontend:
>
> pointspp=# select trid, count(*) from pptran group by trid having
> count(*)
> > 1;
> server closed the connectio
On Thu, 2 Feb 2006, Stephan Szabo wrote:
> On Wed, 1 Feb 2006, Garoso, Fernando wrote:
>
> >
> > The following bug has been logged online:
> >
> > Bug reference: 2231
> > Logged by: Garoso, Fernando
> > Email address: [EMAIL PROTECTED]
On Wed, 1 Feb 2006, Garoso, Fernando wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2231
> Logged by: Garoso, Fernando
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.x
> Operating system: GNU Linux Debian
> Description:Incorrect Ord
On Tue, 17 Jan 2006, Daniel Afonso Heisler wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2178
> Logged by: Daniel Afonso Heisler
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.X
> Operating system: Linux
> Description:NOT IN comm
On Mon, 16 Jan 2006, Vic wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2172
> Logged by: Vic
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.6
> Operating system: FreeBSD 5.4/6.0
> Description:Problem with query in order by
> Deta
On Thu, 27 Oct 2005, David Pujol wrote:
> Hello, I've noticed a bug when I modify a quantity with an INSERT and a
> minus operator.
> My request is:
> UPDATE products SET pr_stock=pr_stock--1 WHERE pr_code=600;
>
> I haven't SQL error but 'pr_stock' value (numeric(5,1)) is unchanged : no
> increme
On Sat, 8 Oct 2005, Tony Marston wrote:
> >
> > If there's two items:
> > "Function" with a description and "Definition" with a
> > definition, I think it's fairly ignorant to read the former
> > as overriding the latter. The latter *is* the definition.
> >
>
> Yes, but if the sample code disagre
On Sat, 8 Oct 2005, Tony Marston wrote:
>
>
>
>
> > -Original Message-
> > From: Stephan Szabo [mailto:[EMAIL PROTECTED]
> > Sent: 08 October 2005 16:44
> > To: Tony Marston
> > Subject: RE: [BUGS] BUG #1937: Parts of information_schema
> >
On Tue, 4 Oct 2005, Tony Marston wrote:
> Description:Parts of information_schema only accessible to owner
> Details:
>
> I have been trying to access parts of the information_schema as an ordinary
> user, not as owner, and I am encountering instances where I cannot retrieve
> any rows at
On Mon, 26 Sep 2005, Tobias Brox wrote:
> We had major problems after migrating the DB to a more powerful server; we
> managed to locate the problem to a type conversion bug in our software.
> Never the less, this thing puzzles us a lot:
>
> NBTEST2=# select '-1'>'0';
> ?column?
> --
> t
On Fri, 16 Sep 2005, Pete Beck wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1886
> Logged by: Pete Beck
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1 & 8.0.3
> Operating system: Linux and Windows
> Description:Bug in SQL par
On Mon, 29 Aug 2005, Christian Almeida wrote:
> Should this sql work?
Yes and no. ;) Whether this errors or adds the reference is controlled by
a configuration variable, add_missing_from. For backwards compatibility
reasons (and for allowing outside table references in delete) the variable
cur
On Mon, 22 Aug 2005, Paul Bramble wrote:
> Is there an easy way to get started so I can quickly install Postgress and
> load my schema?
You didn't say what kind of system you're running, but getting a packaged
version of PostgreSQL (RPM, DEB, Windows Installer) will probably help on
the install
On Sun, 21 Aug 2005, Matt wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1839
> Logged by: Matt
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: linux
> Description:insert into table (column) values (nullif('',
On Fri, 19 Aug 2005, Bernard wrote:
> But we can take this one step further so that we don't even need to
> trust ourselves:
>
> The logical next step is that for a non-postgresql-superuser user,
> COPY FROM files have to be world-readable and COPY TO files and
> directories have to be world-writa
On Fri, 19 Aug 2005, Bernard wrote:
> My suggestions for improving the COPY command so it can be used by
> non-superuser users would be as follows:
If you want to do this without switching to a different UNIX user, can't
you already write a small SECURITY DEFINER function as a superuser that
doe
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
&g
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 Sat, 6 Aug 2005, yoursoft wrote:
> The following bug has been logged online:
>
> Bug reference: 1813
> Logged by: yoursoft
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: SuSE 9.3 professional
> Description:lower() function doesn'
On Sat, 23 Jul 2005, Andrew Smith wrote:
> The following bug has been logged online:
>
> Bug reference: 1781
> Logged by: Andrew Smith
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4.6
> Operating system: Debian GNU/Linux 3.1
> Description:result of casca
On Fri, 15 Jul 2005, David Fetter wrote:
> Here's a repro (psql):
>
> create table foo (foo_id SERIAL PRIMARY KEY, foo_text TEXT NOT NULL);
> CREATE type two_foos AS (foo1 foo, foo2 foo);
> CREATE type four_foos AS (two_foo1 two_foos, two_foo2 two_foos);
> DROP TABLE foo CASCADE;
>
> Perhaps I hav
On Wed, 13 Jul 2005, Herschel Hall wrote:
> The following bug has been logged online:
>
> Bug reference: 1765
> Logged by: Herschel Hall
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7..4
> Operating system: Linux
> Description:Referential Integrity Problem
On Thu, 30 Jun 2005, Daniel Cristian Cruz wrote:
> ALTER TABLE ONLY mat_comissao_itens
> ADD CONSTRAINT mat_nf_saida_itens_pa_mat_comissao_itens FOREIGN KEY
> (mat_nfs_diretorio, mat_nfs_in_codigo, mat_nsi_in_ordem) REFERENCES
> mat_nf_saida_itens(mat_nfs_diretorio, mat_nfs_in_codigo, mat_nsi
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi there,
>
> I was wondering if it is a bug or a feature. When I change a key on a
> referenced table, and there is a foreign key deferred constraint, it
> triggers imediately, not at the end of transaction.
>
> If I change the reference first
On Mon, 27 Jun 2005, Pieter-Jan Savat wrote:
> I was wondering if the following issue is in fact a bug, or just
> inconvenient behaviour...
>
> say a table looks like this:
>
> table
> ---
> c (varchar)
> '20'
> '0'
> '-10'
> 'klj'
> '> 5'
> 'qwerty'
> '< 6'
>
> The query select * from table where
On Fri, 24 Jun 2005, Christian Mercure wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1728
> Logged by: Christian Mercure
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows XP
> Description:unable to connec
On Tue, 7 Jun 2005, Frank van Vugt wrote:
> Looking forward to your analysis of the following bug:
You've analyzed the situation incorrectly I believe.
> -- however, the following query will happily run AND return a wrong result
> -- based on the regular table instead of the temporary one
> sel
On Sun, 29 May 2005, wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1689
> Logged by:
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: Linux
> Description:problem with inheritance and foreign keys
> Details:
>
> -
On Sun, 29 May 2005, wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1688
> Logged by:
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: Linux
> Description:inheritance and foreign key creation problem
> Details:
>
> ---
On Fri, 15 Apr 2005, Nicolas HAHN wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1598
> Logged by: Nicolas HAHN
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4.7
> Operating system: Fedora Core 3
> Description:using default 'now',
On Thu, 7 Apr 2005, Michaela wrote:
> The following bug has been logged online:
>
> Bug reference: 1590
> Logged by: Michaela
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: SuSE Linux 9.1
> Description:Comparison Operation with Stri
On Tue, 29 Mar 2005, Greg Sabino Mullane wrote:
> Not many data points yet, but here's all the occurances:
>
> $ grep "signal 9" 5810.log
> <2005-03-28 03:38:14 EST >LOG: server process (PID 29216) was terminated by
> signal 9
> <2005-03-28 10:15:45 EST >LOG: background writer process (PID 2927
On Mon, 21 Mar 2005, Peter Cottingham wrote:
> Appears that the GROUP BY clause is not working correctly on new server
> (GROUP BY should order the result set in ASCENDING order, NOT DESCENDING
> order.) See below
I do not believe this is a bug. Result sets have no guaranteed ordering
unless yo
On Wed, 23 Mar 2005, Sergio Lob wrote:
> Precision is the number of total digits in the number. Scale is the
> number of fractional digits.
> For instance, a column defined as NUMERIC(10,3) should return
> precision=10, scale=3. The error only occurs for a column defined as
> NUMERIC (without
On Sat, 19 Mar 2005, Roy Badami wrote:
> Roy> I don't have a copy of the spec, but according to "A guide to
> Roy> the SQL standard" conversions like this that would discard
> Roy> data are supposed to raise an exception.
>
> Just to clarify, my understanding is that in ANSI SQL it is
On Fri, 18 Mar 2005, Tom Lane wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
> > It turns out that the scenario above is trivial to hit in 8.0 using
> > referential constraints; RI triggers cache their plans, and on 8.0 the RI
> > query is planned as a seqscan if the tables are freshly cr
On Fri, 18 Mar 2005, Oliver Siegmar wrote:
> On Friday 18 March 2005 14:29, Stephan Szabo wrote:
> > Given the error message, this seems to be the whole plpgsql caches query
> > plans but we don't invalidate those plans when there are schema changes.
>
> I already tr
On Tue, 15 Mar 2005, Oliver Siegmar wrote:
> Here's a demonstration of the bug:
>
> CREATE FUNCTION testfunction()
> RETURNS void
> AS '
> BEGIN
> CREATE TEMP TABLE testtable (field int4) ON COMMIT DROP;
>
> INSERT INTO testtable (field) VALUES (1);
>
> -- DROP TABLE te
On Thu, 3 Mar 2005, DIEGO URRA wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1522
> Logged by: DIEGO URRA
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: REDHAT 6.2
> Description:there's a syntax error using ps
On Tue, 8 Feb 2005, rob wrote:
> We appear to have some kind of problem on one of our internal production
> systems and I can't think were first to look.
>
> What follows is some selects. Note the OID. The column 'id' is primary
> key. The production system makes selects based on status. As you ca
On Tue, 18 Jan 2005, Lutischán Ferenc wrote:
> CREATE TABLE test (
> col1 character varying(10),
> col2 character varying(10)
> );
>
>
> ALTER TABLE ifc.test OWNER TO postgres;
>
> CREATE TABLE test2 (
> col1 character varying(10),
> col2 character varying(10)
> );
>
>
> ALTER TAB
On Thu, 2 Dec 2004, postgresbugs wrote:
>
> On Wed, 1 Dec 2004, Stephan Szabo wrote:
>
> On Wed, 1 Dec 2004, postgresbugs wrote:
>
> > Foreign keys referencing parent table fails on insert if the key is in
> > the table that inherits the parent table.
>
&g
On Wed, 1 Dec 2004, postgresbugs wrote:
> Foreign keys referencing parent table fails on insert if the key is in
> the table that inherits the parent table.
Unfortunately, primary keys, unique constraints and foreign keys do not
inherit to children in a meaningful fashion. It's one of the big
de
On Wed, 1 Dec 2004, PostgreSQL Bugs List wrote:
> Query:
> select 2 union select 1
>
> Result:
> 1
> 2
>
> Why? I think the result must be like this:
> 2
> 1
If you don't specify an order by (at the top level) the output has no
defined order by SQL, so both orders are valid.
> Why PostgreSQL so
On Thu, 25 Nov 2004, Andrzej Wojtaszek wrote:
> I'm afraid that operator ::interval not working propertly
> example:
>
> select 1
> ##
> select now() + (1||' day')::interval;
> working propertly
> ##
This is a text -> interval conversion
> select 3
> #
On Mon, 22 Nov 2004, Stephan Szabo wrote:
> On Mon, 22 Nov 2004, David Schweikert wrote:
>
> > On Sun, Nov 21, 2004 at 20:10:08 -0500, Tom Lane wrote:
> > > I'm not entirely convinced this is a bug. I get the right answer from
> > >
> > > regre
On Mon, 22 Nov 2004, David Schweikert wrote:
> On Sun, Nov 21, 2004 at 20:10:08 -0500, Tom Lane wrote:
> > I'm not entirely convinced this is a bug. I get the right answer from
> >
> > regression=# select to_number('001,000', '999,999') ;
> > to_number
> > ---
> > 1000
> > (1 row)
On Thu, 18 Nov 2004, Cao Duy wrote:
> hi,
>
> I created this table:
> CREATE TABLE public.stresslog(
> "AbfrageId" int8 NOT NULL DEFAULT
> nextval('public."stresslog_AbfrageId_seq"'::text),
> "AbfrageTyp" varchar(50) NOT NULL,
> "Abfrage" varchar(300),
> "AnzZeilen" int8 DEFAULT 0,
> "Ze
On Thu, 18 Nov 2004, PostgreSQL Bugs List wrote:
> select * from tbinvoicerows
> where invoicecd = 'FLOCAA0025'
>
> result in 0 seconde with 2 records NO BUG
>
> select * from tbinvoicerows
> where invoicecd like '%FLOCAA0025%'
>
> result in 40 secondes with 2 records NO BUG
>
> selec
On Tue, 9 Nov 2004, [iso-8859-1] Abaco informática s.a. wrote:
> this sentence is accepted by postgresql sintax analizer but we think
> that's incorrect:
>
> select * from table T where T.field = table.field_1
>
> it take the result as an inner join between 'T' and 'table' which not
> exist ... j
On Sat, 6 Nov 2004, PostgreSQL Bugs List wrote:
> Rows inserted into a table "sub" inherited from a table
> "super" do not seem to exist in the super-table from the point of
> view of the foreign key constraint checker in references to the
> "super"-table, even though a SELECT query displays the r
On Wed, 3 Nov 2004, PostgreSQL Bugs List wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1305
> Logged by: Károly Segesdi
>
> Email address: [EMAIL PROTECTED]
>
> PostgreSQL version: 7.4.5
>
> Operating system: slackware 10.0
>
> Description:ca
e anomalous behaviors that are
> possible now that triggers can fire during the execution of PL
> functions. Stephan Szabo.
>
> Take this test...
> Restricted foreign key allows insertion deferrable,
> And rejects deletion deferrable.
There's two separate co
On Wed, 29 Sep 2004, Aleksey Fedorchenko wrote:
> > IIRC, b2 was before Tom changed the code for doing triggers between
> > function statements, current sources have that code. So, b3 should have
> > the change I mentioned which makes the above work (for immediate
> > constraints).
>
> You're rig
On Sun, 26 Sep 2004, Stephan Szabo wrote:
> What I'm saying is that, constraints are checked at end of statement. In
> current releases (8.0b2 included I believe but not 8.0b3) functions are
> considered part of the statement that called them, so the constraints are
> check
On Sun, 26 Sep 2004, Aleksey Fedorchenko wrote:
> As i told, under pgAdmin's console and PHP it fails anyway but psql
> falls only with function invocation.
Hmm, for PHP was it sent as one big string with all the statements or a
separate statements? There's a side issue that I believe you can s
On Fri, 24 Sep 2004, Alexey Fedorchenko wrote:
> Stephan!
>
> > This is a known issue with the unique constraint.
>
> Ok. Do you know any plans on this issue fix?
>
> > > --case 2 prepare
> > > --case 3 prepare
> >
> > I seem to get foreign key violations on both of these on both 7.4.x and
> > 8.
On Wed, 22 Sep 2004, Markus Feier wrote:
> Dear Sirs
>
> I encountered a minor Postgres problem using VIEW:
>
> Creating a View like
> CREATE VIEW SELECT * FROM table1
> works perfecly
>
> As soon as we enlarge table1 by new Attributes, they will not show up in the
> VIEV
> The VIEW will need to
On Thu, 23 Sep 2004, PostgreSQL Bugs List wrote:
> /* */
> --case 1 prepare
> delete from buggy_uq;
> insert into buggy_uq values (1);
> insert into buggy_uq values (2);
> --case 1 test
> update buggy_uq set i = i + 1;
> select * from buggy_uq;
> --expect - SUCCESS
> --result - ERROR: du
On Sun, 5 Sep 2004 [EMAIL PROTECTED] wrote:
> I found a bug in the behaviour of plpgsql error handling system
> while trying to handle foreign key violation exception.
>
> When this error occured, control doesn't jump to exception handling block.
> It moves to the next statement instead. When con
On Thu, 26 Aug 2004, Gaetano Mendola wrote:
> Stephan Szabo wrote:
>
> > On Wed, 25 Aug 2004, PostgreSQL Bugs List wrote:
> >
> > Actually, it shows that functions have odd behavior when locking is
> > involved (your statement would potentially be true if you could
1 - 100 of 386 matches
Mail list logo
