Hi,
well i just updated the code and found your patch is applied in there and
it's working. may be i missed something while applying your patch.
Regards,
--Asif
On 2/8/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Asif Ali" <[EMAIL PROTECTED]> writes:
> here is the test case
It works for me:
regr
Steven wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2975
> Logged by: Steven
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system: Windows Xp Sp2
> Description:UNIQUE INDEX doesn't work
> Details:
>
> I have a
Michal Schwarz wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2974
> Logged by: Michal Schwarz
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.7
> Operating system: Fedora Core 6
> Description:broken CHECK constraint with varchar
"Marcio A. Sepp" <[EMAIL PROTECTED]> writes:
> It seems to have a problem when making backup and restore with type
> bigserial.
Don't use a pg_dump/pg_restore that are newer than your server version.
regards, tom lane
---(end of broadcast)-
This is a known issue with 8.1.7. 8.1.8 was released shortly after 8.1.7
because of this.
Walter Cruz wrote:
-> The following bug has been logged online:
Bug reference: 2980
Logged by: Walter Cruz
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.7
Operating system:
Roman,
On 2/7/07, Roman Grigorovich <[EMAIL PROTECTED]> wrote:
ERROR: attribute 1 has wrong type
DETAIL: Table has type character varying, but query expects character
varying.
What is it? On version 8.1.2 - ALL OK!
This is a known problem of 8.1.7. That's why 8.1.8 has been released.
So yo
The following bug has been logged online:
Bug reference: 2979
Logged by: Roman Grigorovich
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.7
Operating system: FreeBSD 5.4-RELEASE
Description:Functional indexes ERROR while updating table
Details:
create tabl
> > Upgraded to 8.2.2 last night and had to revert to 8.2.1
> > first thing in the morning after hitting this problem:
>
> Can you try your production case (not just a minimal example) with this
> patch?
> http://archives.postgresql.org/pgsql-committers/2007-02/msg00128.php
The patch didn't apply
Pardon, in this example case it works ok. The problem is when i restore this
structure (this is my real case):
CREATE TABLE fat_m.ped_venda_it
(
cd_ped_venda_it_record bigserial NOT NULL,
...
...
)
When the table is created, the sequence is created too:
CREATE SEQUENCE fat_m.ped_venda_it_
The following bug has been logged online:
Bug reference: 2982
Logged by: Dan Armbrust
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Windows XP
Description:Install broken when not installed as a service
Details:
If you try to install po
The following bug has been logged online:
Bug reference: 2975
Logged by: Steven
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows Xp Sp2
Description:UNIQUE INDEX doesn't work
Details:
I have a unique index on a table, but it is sti
The following bug has been logged online:
Bug reference: 2981
Logged by: Asif
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Fedora 3
Description:server crash
Details:
I have compiled postgres 8.2.1 with gcc 4.1. and when executed this
The following bug has been logged online:
Bug reference: 2980
Logged by: Walter Cruz
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.7
Operating system: Linux
Description:check constraint fails on update
Details:
Hi All. A simple table to test:
CREATE TABL
The following bug has been logged online:
Bug reference: 2974
Logged by: Michal Schwarz
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.7
Operating system: Fedora Core 6
Description:broken CHECK constraint with varchar
Details:
CREATE TABLE t (c VARCHAR(20)
It seems to have a problem when making backup and restore with type
bigserial. I perceived when was restoring a database and the sequence
created for field bigserial was not correctly restored.
For example, i've created the follow structure:
CREATE TABLE cager.princ
(
cd_princ bigserial NOT N
"Asif Ali" <[EMAIL PROTECTED]> writes:
> here is the test case
It works for me:
regression=# select func();
INFO: sql error msg ex -
INFO: sql error msg ex -
INFO: sql error v_msg ex -
func
--
0
(1 row)
Are you sure you applied the patch correctly? In particular, you'd n
here is the test case
CREATE OR REPLACE FUNCTION func() RETURNS int as $$
BEGIN
RAISE EXCEPTION 'ex -';
EXCEPTION
WHEN OTHERS THEN
RAISE INFO 'sql error msg %',sqlerrm;
DECLARE
v_msg VARCHAR(200) := sqlerrm;
BEGIN
RAISE INFO 'sql error msg %',sqlerrm; -- it show's
RAISE INFO 'sql err
"Asif Ali" <[EMAIL PROTECTED]> writes:
> your patch fixes the crash but instead of displaying the sqlerrm value, it
> is displaying in
> pl block, declared inside exception block.
Hm, not what I see here. Could you submit a test case that does that?
regards, tom lane
--
18 matches
Mail list logo