[BUGS] BUG #6316: function search_path causes set_config() is_local = true to have no effect

[postgresql]

The following bug has been logged on the website:

Bug reference:  6316
Logged by:  Jon Erdman
Email address:  postgre...@thewickedtribe.net
PostgreSQL version: 9.1.1
Operating system:   Ubuntu
Description:


Hi Tom! :)

So, found this in 8.3 but tested and it effects everything up to 9.1.1. If
search_path on a function is set to anything, calls to set_config() with
is_local = true inside that function have no effect. 

See test case and output below:

BEGIN;

CREATE OR REPLACE FUNCTION public.setting_bug_true()
RETURNS VOID LANGUAGE plpgsql AS
$$
BEGIN
PERFORM pg_catalog.set_config( 'search_path', 'pg_catalog', 
true );
END;
$$
SET search_path = public
;

CREATE OR REPLACE FUNCTION public.setting_bug_false()
RETURNS VOID LANGUAGE plpgsql AS
$$
BEGIN
PERFORM pg_catalog.set_config( 'search_path', 'pg_catalog', 
false );
END;
$$
SET search_path = public
;

SET search_path = public;
SHOW search_path;

SELECT public.setting_bug_true();
\echo Search path should now be pg_catalog
SHOW search_path;

SET search_path = public;
SHOW search_path;

SELECT public.setting_bug_false();
\echo Oddly, if is_local is false, it *does* work
SHOW search_path;

ALTER FUNCTION public.setting_bug_true() SET search_path = DEFAULT;

SET search_path = public;
SHOW search_path;

SELECT public.setting_bug_true();
\echo Take search_path off the function and it works!?! /me smells a bug...
SHOW search_path;

ROLLBACK;





And the output:

postgres@[local]/cnuapp_dev:5437=# \i ~/bug.sql
BEGIN
Time: 0.070 ms
CREATE FUNCTION
Time: 0.208 ms
CREATE FUNCTION
Time: 0.164 ms
SET
Time: 0.055 ms
 search_path
-
 public
(1 row)

Time: 0.025 ms
 setting_bug_true
--

(1 row)

Time: 0.138 ms
Search path should now be pg_catalog
 search_path
-
 public
(1 row)

Time: 0.022 ms
SET
Time: 0.019 ms
 search_path
-
 public
(1 row)

Time: 0.023 ms
 setting_bug_false
---

(1 row)

Time: 0.085 ms
Oddly, if is_local is false, it *does* work
 search_path
-
 pg_catalog
(1 row)

Time: 0.021 ms
ALTER FUNCTION
Time: 0.051 ms
SET
Time: 0.014 ms
 search_path
-
 public
(1 row)

Time: 0.018 ms
 setting_bug_true
--

(1 row)

Time: 0.108 ms
Take search_path off the function and it works!?! /me smells a bug...
 search_path
-
 pg_catalog
(1 row)

Time: 0.018 ms
ROLLBACK
Time: 0.050 ms
postgres@[local]/cnuapp_dev:5437=#



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8393: "ERROR: failed to locate grouping columns" on grouping by varchar returned from function

[postgresql]

The following bug has been logged on the website:

Bug reference:  8393
Logged by:  Evan Martin
Email address:  postgre...@realityexists.net
PostgreSQL version: 9.2.4
Operating system:   Windows 7 x64 SP1
Description:

version(): PostgreSQL 9.2.4, compiled by Visual C++ build 1600, 64-bit


Run the following:


CREATE OR REPLACE FUNCTION test_group_by()
RETURNS TABLE (my_col varchar(5))
AS $BODY$
SELECT 'hello'::varchar(5);
$BODY$ LANGUAGE sql STABLE;


SELECT my_col
FROM test_group_by()
GROUP BY 1;




Expected result:


'hello'


Actual result:


ERROR:  failed to locate grouping columns


Interestingly, if the function is marked "VOLATILE" it works. Casting the
result to "text" also makes it work.



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8467: Slightly confusing pgcrypto example in docs

[postgresql]

The following bug has been logged on the website:

Bug reference:  8467
Logged by:  Richard Neill
Email address:  postgre...@richardneill.org
PostgreSQL version: 9.3.0
Operating system:   Documentation bug
Description:

The documentation for pgcrypto: 
http://www.postgresql.org/docs/current/static/pgcrypto.html
(and indeed all versions from 8.3-9.3)
contains the following:



Example of authentication:


SELECT pswhash = crypt('entered password', pswhash) FROM ... ;


This returns true if the entered password is correct.



I found this confusing, because it's  using the same name, "pswhash" in 2
places, one of which is a boolean. It would be, imho, clearer to write the
example query as:



SELECT is_authenticated = crypt('entered password', pswhash) FROM ... ;



[Also, should the default example perhaps use gen_salt('bf'), as opposed to
gen_salt('md5') ?]




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8213: Set-valued function error in union

[eric-postgresql]

The following bug has been logged on the website:

Bug reference:  8213
Logged by:  Eric Soroos
Email address:  eric-postgre...@soroos.net
PostgreSQL version: 9.0.13
Operating system:   Ubuntu 10.04, 32bit
Description:

This has been replicated on 9.2.4 and HEAD by ilmari_ and johto.

erics@dev:~/trunk/sql$ psql -a -h 192.168.10.249 -f pg_bug_report.sql
\set VERBOSITY verbose
\set echo all
select version();
  version   
   

 PostgreSQL 9.0.13 on i686-pc-linux-gnu, compiled by GCC gcc-4.4.real
(Ubuntu 4.4.3-4ubuntu5) 4.4.3, 32-bit
(1 row)

-- this fails. I'd expect it to succeed. 
select id, dt from
   (select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day')::date as dt
union
select 2, now()::date
) as foo
where dt < now()+'15 days'::interval;
psql:pg_bug_report.sql:13: ERROR:  0A000: set-valued function called in
context that cannot accept a set
LOCATION:  ExecMakeFunctionResult, execQual.c:1733
-- this succeeds, but returns a timestamp
select id, dt from
   (select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day') as dt
union
select 2, now()::date
) as foo
where dt < now()+'15 days'::interval;
 id | dt  
+-
  1 | 2013-06-05 00:00:00
  1 | 2013-06-06 00:00:00
  1 | 2013-06-07 00:00:00
  1 | 2013-06-08 00:00:00
  1 | 2013-06-09 00:00:00
  1 | 2013-06-10 00:00:00
  1 | 2013-06-11 00:00:00
  1 | 2013-06-12 00:00:00
  1 | 2013-06-13 00:00:00
  1 | 2013-06-14 00:00:00
  1 | 2013-06-15 00:00:00
  1 | 2013-06-16 00:00:00
  1 | 2013-06-17 00:00:00
  1 | 2013-06-18 00:00:00
  1 | 2013-06-19 00:00:00
  1 | 2013-06-20 00:00:00
  2 | 2013-06-05 00:00:00
(17 rows)

--this also succeeds, without the where clause
select id, dt from
   (select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day')::date as dt
union
select 2, now()::date
) as foo;
 id | dt 
+
  1 | 2013-06-05
  1 | 2013-06-06
  1 | 2013-06-07
  1 | 2013-06-08
  1 | 2013-06-09
  1 | 2013-06-10
  1 | 2013-06-11
  1 | 2013-06-12
  1 | 2013-06-13
  1 | 2013-06-14
  1 | 2013-06-15
  1 | 2013-06-16
  1 | 2013-06-17
  1 | 2013-06-18
  1 | 2013-06-19
  1 | 2013-06-20
  1 | 2013-06-21
  1 | 2013-06-22
  1 | 2013-06-23
  1 | 2013-06-24
  1 | 2013-06-25
  1 | 2013-06-26
  1 | 2013-06-27
  1 | 2013-06-28
  1 | 2013-06-29
  1 | 2013-06-30
  1 | 2013-07-01
  1 | 2013-07-02
  1 | 2013-07-03
  1 | 2013-07-04
  1 | 2013-07-05
  2 | 2013-06-05
(32 rows)

--this also succeeds, without the union
select id, dt from
   (select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day')::date as dt
) as foo
where dt < now()+'15 days'::interval;
 id | dt 
+
  1 | 2013-06-05
  1 | 2013-06-06
  1 | 2013-06-07
  1 | 2013-06-08
  1 | 2013-06-09
  1 | 2013-06-10
  1 | 2013-06-11
  1 | 2013-06-12
  1 | 2013-06-13
  1 | 2013-06-14
  1 | 2013-06-15
  1 | 2013-06-16
  1 | 2013-06-17
  1 | 2013-06-18
  1 | 2013-06-19
  1 | 2013-06-20
(16 rows)

-- this is the workaround.
select id, dt from
   (select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day')::date as dt
union all
select 2, now()::date
) as foo
where dt < now()+'15 days'::interval;
 id | dt 
+
  1 | 2013-06-05
  1 | 2013-06-06
  1 | 2013-06-07
  1 | 2013-06-08
  1 | 2013-06-09
  1 | 2013-06-10
  1 | 2013-06-11
  1 | 2013-06-12
  1 | 2013-06-13
  1 | 2013-06-14
  1 | 2013-06-15
  1 | 2013-06-16
  1 | 2013-06-17
  1 | 2013-06-18
  1 | 2013-06-19
  1 | 2013-06-20
  2 | 2013-06-05
(17 rows)

-- this is another workaround:
begin; 
BEGIN
create temp view gs as
   select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day') as dt;
CREATE VIEW
create temp view container as
   select id, dt::date from gs
   union
   select 2, now()::date;
CREATE VIEW
select * from container where dt < now()+'15 days'::interval; 
 id | dt 
+
  1 | 2013-06-05
  1 | 2013-06-06
  1 | 2013-06-07
  1 | 2013-06-08
  1 | 2013-06-09
  1 | 2013-06-10
  1 | 2013-06-11
  1 | 2013-06-12
  1 | 2013-06-13
  1 | 2013-06-14
  1 | 2013-06-15
  1 | 2013-06-16
  1 | 2013-06-17
  1 | 2013-06-18
  1 | 2013-06-19
  1 | 2013-06-20
  2 | 2013-06-05
(17 rows)

rollback;
ROLLBACK
-- another workaround
select id, dt from
   (select 1 as id, generate_series(now()::date, now()::date + '1
month'::interval, '1 day')::date as dt
union
select 2, now()::date offset 0
) as foo
where dt < now()+

[BUGS] BUG #1000: Testing new bugs form.

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1000
Logged by:  Dave Page
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.5 Dev
Operating system:   FreeBSD www.postgresql.com 4.8-STABLE FreeBSD 4.8-STABLE #5: Sat 
Sep 20 14:56:14 ADT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/kernel  i386
Description:Testing new bugs form.
Details: 

This is a test sent from the new bug reporting form at 
http://www.postgresql.org/bugform.php.

I'd appreciate an email from someone to let me know that this made it onto the bugs 
list OK as I'm not currently subscribed.

Cheers, Dave.

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1001: Inconsistent authentication between psql and PQconnectdb - possible security implications?

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1001
Logged by:  Alan W. Irwin
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Debian stable (Linux)
Description:Inconsistent authentication between psql and PQconnectdb - 
possible security implications? 
Details: 

I use "ident sameuser" authentication.  Here are the relevant details from pg_hba.conf.

local   all all ident sameuser
hostall all 127.0.0.1 255.255.255.255   ident sameuser
hostall all 0.0.0.0   0.0.0.0   reject

All is well with psql authentication.  However, when I tried to
use knoda/hk_classes to access the database, I could not get authenticated.  A typical 
error message was IDENT authentication failed for user "irwin".  When I traced this 
down through the hk_classes code it was using PQconnectdb to connnect to the database, 
and there were complaints in the postgresql log that the identd server was not 
available.  All knoda/hk_classes/PQconnectdb problems disappeared when I installed 
identd (apt-get install pidentd) on my Debian stable system.  So all seems well when 
identd is installed, but there may be a security concern with psql when it is not.  On 
the other hand, if psql is actually secure when identd is not running, then why isn't 
PQconnectdb using the exact same (secure) method of authentication for this case?

Note, this authentication inconsistency between psql and PQconnectdb  in the absence 
of an identd server occurs both for a postgresql-7.4 version that I built and 
installed myself and also for the Debian stable version (7.2.1-2woody4) of postgresql.


---(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

[BUGS] BUG #1002: Update using rule on view with inheritance alters 0 rows, 1 row expected.

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1002
Logged by:  Chris Piker
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   RedHat Linux 9
Description:Update using rule on view with inheritance alters 0 rows, 1 row 
expected.
Details: 

Specific Version 

Using postgres binary distribution that includes the
file: postgresql-7.4-0.3PGDG.i386.rpm


Schema (with data)
--

-- Groups and Permissions tables

create table groups(
   gid int4 primary key,
   short_name varchar(32)
);

create table perms(
   gid integer not null references groups(gid)
  on update cascade on delete cascade,
   usename name not null,
   primary key (gid, usename),

   sel boolean not null,
   ins boolean not null,
   up boolean not null,
   del boolean not null
);


-- Data Object Tables...

create table base(
   id integer primary key,
   gid integer references groups(gid)
  on update cascade on delete set null,
   obj_name varchar(128) not null
);

create table child_1(
   primary key(id),
   foreign key(gid) references groups(gid)
  on update cascade on delete set null,
   child1_stuff text
) inherits (base);

create table child_2(
   primary key(id),
   foreign key(gid) references groups(gid)
  on update cascade on delete set null,
   child2_stuff text
) inherits (child_1);

-- Data for permission tables:

insert into groups 
   values (1,'users');
insert into perms 
   values (1,'postgres',true,true,true,true);

-- Data for object tables:
insert into base 
   values (1,1,'Base Object');
insert into child_1 
   values (2,1,'Child 1 Object','Stuff');
insert into child_2 
   values (3,1,'Child 2 Object','Stuff','Stuff');


-- Update view on table "base"

create view base_up as select base.* from perms,base where
   perms.gid = base.gid and 
   perms.usename = session_user and
   perms.up = true;

create rule R_base_up as on update to base_up 
   do instead update base set 
   gid = new.gid, 
   obj_name = new.obj_name
   where old.id = id;

grant select,update on base_up to public;


Problem Query
-
The following query updates 0 rows, when 1 row is 
expected to be updated:

update base_up set obj_name = 'new name' where id = 3;

The following related query updates 1 row, when 1 row
is expected:

update base_up set obj_name = 'new name' where id = 2;

Explain clearly shows which parts of the query plan are
in error.  I can send the explain analyze output if 
needed.

Thanks for your time on this issue.
--
[EMAIL PROTECTED]





---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1003: postgres config error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1003
Logged by:  hemachandra
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3
Operating system:   Red Hat8.0
Description:postgres config error
Details: 

I have installed the Postgres by the procedure by.
 it got installed at /usr/local/pgsql/bin
but, when i re-start the system. the postgres service  starts from /usr/bin.

what shall i do i have tried it by editing the 
 /etc/rc.d/inid.d / postgresql file.
but no result

regards 
hemu



---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1004: configure failure with --infodir=

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1004
Logged by:  Andrew Benham
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   RedHat Linux 3AS
Description:configure failure with --infodir=
Details: 

Line 819 of the 'configure' file tells me that I can
use "--infodir=DIR" as an argument to configure.

However lines 439 and 441 don't accept "--infodir=",
the nearest they'll accept is "--infodi=".



---(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

[BUGS] BUG #1005: JDBC cancelRowUpdates() sets column values to null

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1005
Logged by:  Lars Tetzlaff
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   linux 2.4.23 i686
Description:JDBC cancelRowUpdates() sets column values to null
Details: 

this sequence sets all but "plz" and "kategorie" to null, "kategorie" is changed to 0

  rs.first();
  rs.updateInt( "plz", 9 );
  rs.cancelRowUpdates();
  rs.updateInt( "plz", 6 );
  rs.updateRow();
  rs.beforeFirst();

Output before update:

  Kunde Lars Tetzlaff
  PLZ/Ort 51702 Bergneustadt
  Straße Bahnhofstr. 32 E
  Kategorie 1


Output after Update

 Kunde null
 PLZ/Ort 6 null
 Straße null
 Kategorie 0

If i comment out the second updateInt, the data is OK.


java version "1.4.2_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)


Table:

create table kunde
(
name varchar( 30 ) not null primary key,
plz integer,
ort varchar(30),
strasse varchar( 30 ),
kategorie integer not null
);

insert into kunde values ( 'Lars Tetzlaff', 51702, 'Bergneustadt', 'Bahnhofstr. 32 E', 
1 );



Programm:

import java.sql.*;

public class connect
{
public static void main( String argv[] )
{
try {

//Class.forName("org.postgresql.Driver");
Connection db = DriverManager.getConnection( "jdbc:postgresql:tetzlaff",
 "tetzlaff", "");

db.setAutoCommit( false );

//  PreparedStatement pst = db.prepareStatement("insert into kunde values ( ?, 
" +
//"?, ?, ?, ? )");

//  pst.setString( 1, "Thomas Friese" );
//  pst.setInt( 2, 51580 );
//  pst.setString( 3, "Reichshof-Eckenhagen" );
//  pst.setString( 4, "Landwehrstr. 7" );
//  pst.setInt( 5, 3 );

//  pst.executeUpdate();

Statement st = db.createStatement( ResultSet.TYPE_SCROLL_SENSITIVE,
   ResultSet.CONCUR_UPDATABLE );

ResultSet rs = st.executeQuery("SELECT * FROM kunde");

if( rs.isBeforeFirst() ) {
System.out.println( "Alles klar" );
}
else{
System.out.println( "Wo bin ich denn?" );
}

while (rs.next()) {
//System.out.print("Column 1 returned ");
System.out.println( "Kunde " + rs.getString(1) 
+ "\nPLZ/Ort " 
+ rs.getInt(2) + " " + rs.getString(3)
+ "\nStraße " +rs.getString( "STRASSE" ) 
+ "\nKategorie " + rs.getInt( "kategorie" )
);
}

rs.first();
rs.updateInt( "plz", 9 );
rs.cancelRowUpdates();
rs.updateInt( "plz", 6 );
rs.updateRow();
rs.beforeFirst();

while (rs.next()) {
//System.out.print("Column 1 returned ");
System.out.println( "Kunde " + rs.getString(1) 
+ "\nPLZ/Ort " 
+ rs.getInt(2) + " " + rs.getString(3)
+ "\nStraße " +rs.getString( "STRASSE" )
+ "\nKategorie " + rs.getInt( "kategorie" )
);
}

rs.close();
st.close();
}
catch( Exception ex ){
System.out.println( "Exception" + ex );
}

}
}


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1006: information schema constraint information.

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1006
Logged by:  Majolee InfoTech
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Redhat 9.0
Description:information schema constraint information.
Details: 

Hello,

as per the documentation of information schema (constraint_column_usage) view should 
return exact column names for a constraint created. 

Currently this view has a bug for foreign key constraints created for a table for more 
than one times. It shows first inserted column name for all of the following foreign 
keys defined for same table.
#
CREATE TABLE public.test
(
  fld1 varchar(25) NOT NULL,
  fld2 varchar(25),
  fld3 varchar(25),
  CONSTRAINT pk1 PRIMARY KEY (fld1)
) WITH OIDS;
CREATE TABLE public.test2
(
  pk2 int8 NOT NULL,
  fk1 varchar(25),
  CONSTRAINT pk22 PRIMARY KEY (pk2),
  CONSTRAINT fk11 FOREIGN KEY (fk1) REFERENCES public.test (fld1) ON UPDATE RESTRICT 
ON DELETE RESTRICT
) WITH OIDS;
CREATE TABLE public.test3
(
  fld_1 varchar(25) NOT NULL,
  fld_2 varchar(25) NOT NULL,
  fld_3 varchar(25) NOT NULL,
  CONSTRAINT pk3 PRIMARY KEY (fld_1),
  CONSTRAINT fk3_1 FOREIGN KEY (fld_2) REFERENCES public.test (fld1) ON UPDATE 
RESTRICT ON DELETE RESTRICT,
  CONSTRAINT fk3_2 FOREIGN KEY (fld_3) REFERENCES public.test2 (pk2) ON UPDATE 
RESTRICT ON DELETE RESTRICT
) WITH OIDS;
#

This on querying
#
select * from information_schema.constraint_column_usage
#

gives following output

#
table_catalog | table_schema | table_name | column_name | constraint_catalog | 
constraint_schema | constraint_name
---+--++-++---+-
 ERP   | public   | test   | fld1| ERP| public 
   | pk1
 ERP   | public   | test2  | pk2 | ERP| public 
   | pk22
 ERP   | public   | test2  | pk2 | ERP| public 
   | fk11
 ERP   | public   | test3  | fld_1   | ERP| public 
   | pk3
 ERP   | public   | test3  | fld_1   | ERP| public 
   | fk3_1
 ERP   | public   | test3  | fld_1   | ERP| public 
   | fk3_2
#

Which should show (Changes displayed within *CHANGE*)

#
table_catalog | table_schema | table_name | column_name | constraint_catalog | 
constraint_schema | constraint_name
---+--++-++---+-
 ERP   | public   | test   | fld1| ERP| public 
   | pk1
 ERP   | public   | test2  | pk2 | ERP| public 
   | pk22
 ERP   | public   | test2  | *fk1* | ERP| 
public| fk11
 ERP   | public   | test3  | fld_1   | ERP| public 
   | pk3
 ERP   | public   | test3  | *fld_2*   | ERP| 
public| fk3_1
 ERP   | public   | test3  | *fld_3*   | ERP| 
public| fk3_2
#

Please update us on the same.

Thanks.

Majolee InfoTech

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1007: error during installation

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1007
Logged by:  Wong Choon Hen
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Windows XP
Description:error during installation
Details: 

When running the following command as instructed:-

nmake -f win32.mak

I got the error message as follows:-

This application has failed to start because mspdb71.dll was not found. Re-installing 
the application may fix this problem.

Please advise.


Thanks & regards

---(end of broadcast)---
TIP 8: explain analyze is your friend

[BUGS] BUG #1008: fe-misc.c has an ifdef for HAVE_POLL, should be HAVE_POLL_H

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1008
Logged by:  Peter Herndon
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Mac OS X 10.3.1
Description:fe-misc.c has an ifdef for HAVE_POLL, should be HAVE_POLL_H
Details: 

With stock 7.4, configure options --prefix=/usr/local --with-rendezvous --with-openssl 
--with-includes=/sw/include --with-libraries=/sw/lib, make failes on 
src/interfaces/libpq/fe-misc.c, complaining of undefined functions and constants in 
and around line 1011, pqSocketPoll function.  I poked around my config.log and 
config.status, and my OS, and found no trace of poll.h, instead I have select.h.  Yet 
the function was crashing the compile in lines looking for poll.h.  I looked at the 
source a bit more and noticed that the #ifdef was looking for HAVE_POLL, and that 
everything in configure.*, as well as the top of fe-misc.c, was looking at 
HAVE_POLL_H.  So I changed line 1011 to HAVE_POLL_H and the compile succeeds.

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1009: ERROR: could not open segment 1 of relation...

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1009
Logged by:  Christopher Hodson
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   freebsd 5.2
Description:ERROR:  could not open segment 1 of relation...
Details: 

I have a script that processes a bit of data.  I've been working on this script since 
7.2 or soa nd have had no database problems.  After upgrading to 7.4 I seem to have a 
problem every run (which may mean calling this scripts several times).

The errors are similar to:
"psql:daily_update.sql:332: ERROR:  could not open segment 1 of relation 
"summ_stubcount" (target block 3538944): No such file or directory"

Note that summ_stubcount is an index.

The error usually occurs within running the script the first few times and the actualy 
query it blows up on varies.

I'm not sure what info would be helpful here.  I would be happy to provide any more 
information I can.

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1010: format_type errors oin formatting type interval.

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1010
Logged by:  Jeff Davis
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Linux, Mac OS X 10.3
Description:format_type errors oin formatting type interval.
Details: 

head=# select version();
version

 PostgreSQL 7.4 on powerpc-apple-darwin7.0.0, compiled by GCC gcc (GCC) 3.3 20030304 
(Apple Computer, Inc. build 1495)

head=# select pg_catalog.format_type(oid, typlen) from pg_type where typname = 
'interval';
ERROR:  invalid INTERVAL typmod: 0xc

Same error on linux.  Does not happen on 7.3.4.


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1011: Explain analyze "query" cause segv

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1011
Logged by:  Pawel Rutkowski
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   FreeBSD rsc.pl 4.9-STABLE FreeBSD 4.9-STABLE #22: Tue Dec  2 
20:31:00 CET 2003
Description:Explain analyze "query" cause segv
Details: 

I've notice problem with some explain analyze queries.
First explain works great but running same explain once again cause Segmentation Fault.

I've test it on two machines (Celeron 1.7GHz 1GB RAM, 2xPIII 1.1GHz 512MB RAM) with 
same result.

There is test case (notice there is ltree column):
(its also avaiable at: http://www.manifest.pl/case.sql)

CREATE TABLE p (
id serial NOT NULL,
kat ltree NOT NULL,
name text,
id_pricelist integer,
manufactur character varying(50),
weight character varying(20),
price double precision,
stock text,
id_pricelist_int integer,
manufactur_code character varying(50) NOT NULL
);

COPY p (id, kat, name, id_pricelist, manufactur, weight, price, stock, 
id_pricelist_int, manufactur_code) FROM stdin;
1364380  root.tillbeh___oumlr.h___oumlgtalare Speaker Soundwave 3000P 5.1 20W 
SUB 5W Center 4x5W Satelite RMS   15 TRUST498   13 15 12951
1364353  root.tillbeh___oumlr.h___oumlgtalare Speaker Soundwave 350P 2x2W RMS 
350W PMPO Retail   15 TRUST130   4  16 13026
1364354  root.tillbeh___oumlr.h___oumlgtalare Speaker SoundWave 450P 2x3W RMS 
450W PMPO Retail   15 TRUST166   9  16 13028
1364352  root.tillbeh___oumlr.h___oumlgtalare Speaker SoundWave 200P 2x2W RMS 
Retail15 TRUST137   8  16 12558
1366057  root.tillbeh___oumlr.h___oumlgtalare Trust Speakers SoundWave 100p 16 
TRUST68 2003-12-17  16 12605
1364378  root.tillbeh___oumlr.h___oumlgtalare Speaker SoundWave 1000P Retail   
15 TRUST177   19 15 12616
1364379  root.tillbeh___oumlr.h___oumlgtalare Speaker SoundWave 2000P 5.1 
Retail  15 TRUST353   2  15 12618
1367533  root.tillbeh___oumlr.h___oumlgtalare Hvgtalare i trd, 300W PMPO, 
aktiv   18 MEGAPART80 918   18 SP-100
1367534  root.tillbeh___oumlr.h___oumlgtalare Hvgtalare i trd, 300W PMPO, 
aktiv, svart  18 MEGAPART80 0  18 SP-101
1367535  root.tillbeh___oumlr.h___oumlgtalare Subwooferpaket i trd, 800W PMPO, 
20W RMS  18 MEGAPART200   211   18 SP-300
\.
EXPLAIN ANALYZE select a.manufactur from p a where kat ~ 
'root.tillbeh___oumlr.h___oumlgtalare.*' group by manufactur order by 
lower(manufactur);
EXPLAIN ANALYZE select a.manufactur from p a where kat ~ 
'root.tillbeh___oumlr.h___oumlgtalare.*' group by manufactur order by 
lower(manufactur);


and here is backtrace from gdb:
(also avaiable at http://www.manifest.pl/bt.txt)
#0  0x81ca0ef in AllocSetAlloc (context=0x83ae120, size=38) at aset.c:546
546 if (chunk->size >= size)
(gdb) bt
#0  0x81ca0ef in AllocSetAlloc (context=0x83ae120, size=38) at aset.c:546
#1  0x81ca931 in MemoryContextAlloc (context=0x83ae120, size=38) at mcxt.c:485
#2  0x81a331e in textout (fcinfo=0xbfbfea84) at varlena.c:285
#3  0x81c16ba in FunctionCall3 (flinfo=0x8411528, arg1=138125792, arg2=0, 
arg3=4294967295) at fmgr.c:1016
#4  0x8081c59 in printtup (tuple=0x83ba1b0, typeinfo=0x8389c18, self=0x83b1778) at 
printtup.c:337
#5  0x8165e27 in RunFromStore (portal=0x83b5018, direction=ForwardScanDirection, 
count=0, dest=0x83b1778) at pquery.c:695
#6  0x8165c51 in PortalRunSelect (portal=0x83b5018, forward=1, count=2147483647, 
dest=0x83b1778) at pquery.c:573
#7  0x8165b66 in PortalRun (portal=0x83b5018, count=2147483647, dest=0x83b1778, 
altdest=0x83b1778, completionTag=0xbfbfecd4 "")
at pquery.c:467
#8  0x8162c7b in exec_simple_query (
query_string=0x83b1018 "EXPLAIN ANALYZE select a.manufactur from p a where kat ~ 
'root.tillbeh___oumlr.h___oumlgtalare.*' group by manufactur order by 
lower(manufactur);") at postgres.c:873
#9  0x816501f in PostgresMain (argc=4, argv=0x8335488, username=0x8335458 "rsctest") 
at postgres.c:2868
#10 0x8144a0d in BackendFork (port=0x8332600) at postmaster.c:2558
#11 0x814422b in BackendStartup (port=0x8332600) at postmaster.c:2201
#12 0x8142b13 in ServerLoop () at postmaster.c:1113
#13 0x8142597 in PostmasterMain (argc=1, argv=0x8322040) at postmaster.c:891
#14 0x8118fd3 in main (argc=1, argv=0xbfbffc94) at main.c:214

Regards
Pawel

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

[BUGS] BUG #1012: missing server/*.h on suse devel rpm package

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1012
Logged by:  Böjthe Zoltán
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Linux Suse 9.0
Description:missing server/*.h on suse devel rpm package
Details: 

the /usr/include/pgsql/server/* include files is missing from 
postgresql-devel-7.4-0.i586.rpm on SuSE 9.0


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1013: Authentication doesn't work

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1013
Logged by:  Keith Hankin
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Fedora Linux
Description:Authentication doesn't work
Details: 

When I start up psql, if I am not not logged in as the owner of the database, I get 
the following error message, even if I type the correct password:

psql: FATAL:  IDENT authentication failed for user "keith"

However, when I start up psql logged in as the owner of the database, I get a proper 
login regardless of whether I type the proper password or not.


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1014: postgres crash

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1014
Logged by:  vidhya
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.3
Operating system:   windows2000
Description:postgres crash
Details: 

Hi,

Due to overload postgres crashes often. I am getting the following error

IpcMemoryCreate: shmget(key=5432001, size=1499136, 03600) failed: Not enough core

I want to increase the SHMMAX parameter in kernel.

I read the PG documents. They suggested to change the parameter in shm.h file.

They told that SHMMAX parameter is defined in shm.h as
“#define SHMMAX 0x200.” 

But i couldn't find such an entry in that file.

Can u suggest me a solution for this?


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1015: Got a signal 11 while trying to create a temp table

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1015
Logged by:  Aarjan Langereis
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.4
Operating system:   RedHat Linux 9 kernel 2.4.20-20.9
Description:Got a signal 11 while trying to create a temp table
Details: 

I tried to create a temp table and got my back-end restarting because of a signal 11.

The 3 tables involved:

CREATE TABLE hosts (
hostID serial primary key,
hostip cidr NOT NULL,
hostname varchar(50),
lastseen timestamp without time zone default ('1970-01-01 01:00'),
total integer default 0,
image varchar(20) default 'hosts/unknown.png'
);
CREATE TABLE cpus (
cpuID integer primary key,
cpuname varchar(20),
lastseen timestamp without time zone default ('1970-01-01 01:00'),
total integer default 0,
image varchar(20) default 'cpus/unknown.png'
);
CREATE TABLE blocks (
blockID varchar(30) primary key,
blockdate timestamp without time zone NOT NULL,
hostID integer REFERENCES hosts,
orgIP cidr NOT NULL,
email varchar(30) NOT NULL,
osID integer  NOT NULL,
cpuID integer NOT NULL,
version integer NOT NULL,
core integer NOT NULL,
amount integer NOT NULL
);

Hosts has 205 rows
Cpus has 17 rows
And blocks has 3194409 rows

This is the problem query:

Create TEMP table tmphosts AS
  select hosts.hostid, hosts.hostip, hosts.hostname, max(blockdate) as lastseen, 
sum(amount) as total, hosts.image
from hosts left join blocks on hosts.hostid=blocks.hostid
group by hosts.hostid, hosts.hostip, hosts.hostname, hosts.image;

But even without the first line is does not work. However this query does work 
properly:

Create TEMP table tmpcpus AS
  select cpus.cpuid, cpuname, max(blockdate) as lastseen, sum(amount) as total, 
image
   from cpus left join blocks on cpus.cpuid=blocks.cpuid
   group by cpus.cpuid, cpuname, image;
They look rather the same to me… But with the first one I got this error in psql:

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.
!# 

In the log was this:

LOG:  server process (pid 27196) was terminated by signal 11
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing shared memory and semaphores
FATAL:  The database system is starting up
LOG:  database system was interrupted at 2003-12-18 19:16:21 CET
LOG:  checkpoint record is at 6/9312CD40
LOG:  redo record is at 6/9312CD40; undo record is at 0/0; shutdown FALSE
LOG:  next transaction id: 2909; next oid: 15667926
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 6/9312CD80
LOG:  ReadRecord: unexpected pageaddr 6/8B162000 in log file 6, segment 147, offset 
1449984
LOG:  redo done at 6/9315EE4C
LOG:  database system is ready

I don’t know what information can be useful to you. But if you need more, please ask!

It seems to me, and please correct me if I’m wrong, that there is a limit to the 
size that a join can handle.

I hope that the information provided is of any use to you.

Yours,

Aarjan


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1016: incomplete src/bin/pgtclsh/Makefile

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1016
Logged by:  Patrick Samson
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.5
Operating system:   Cygwin
Description:incomplete src/bin/pgtclsh/Makefile
Details: 

"make install" fails on cygwin for pgtclsh:

in src/bin/pgtclsh/Makefile, add $(X) to the end of every occurrence of 'pgtclsh' and 
'pgtksh' as part of a command.

Example:
$(INSTALL_PROGRAM) pgtclsh$(X) $(DESTDIR)$(bindir)/pgtclsh$(X)


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1017: Incomplete src/interfaces/libpgtcl/Makefile

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1017
Logged by:  Patrick Samson
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.5
Operating system:   Cygwin
Description:Incomplete src/interfaces/libpgtcl/Makefile
Details: 

For "configure --with-tcl --without-tk".
'make' doesn't know how to resolve references to
Tcl_XXX functions.

In src/interfaces/libpgtcl/Makefile:
Change:
 SHLIB_LINK = $(libpq)
To:
 SHLIB_LINK = $(TCL_LIB_SPEC) $(libpq)


---(end of broadcast)---
TIP 8: explain analyze is your friend

[BUGS] BUG #1018: Incomplete src/pl/tcl/Makefile

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1018
Logged by:  Patrick Samson
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.5
Operating system:   Cygwin
Description:Incomplete src/pl/tcl/Makefile
Details: 

For "configure --with-tcl --without-tk".
'make' doesn't know how to resolve references to
a lot of postgres functions.

In src/pl/tcl/Makefile:
Change:
# link command for a shared lib must NOT mention shared libs it uses
SHLIB_LINK = $(TCL_LIB_SPEC)
To:
# link command for a shared lib must NOT mention shared libs it uses
SHLIB_LINK = $(BE_DLLLIBS) $(TCL_LIB_SPEC)


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1019: src/pl/tcl/pltcl.c

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1019
Logged by:  Patrick Samson
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.5
Operating system:   Cygwin
Description:src/pl/tcl/pltcl.c
Details: 

For "configure --with-tcl --without-tk".
'make' doesn't know how to resolve some references.

make[3]: Entering directory `/opt/postgresql-7.3.5/src/pl/tcl'
dlltool --export-all --output-def pltcl.def pltcl.o
dllwrap -o pltcl.dll --dllname pltcl.dll --def pltcl.def pltcl.o 
../../../src/utils/dllinit.o -L/usr/local/lib -L../../../src/backend -lpostgres 
-L/usr/lib -ltcl84
fu01.o(.idata$3+0xc): undefined reference to `_libpostgres_a_iname'
fu03.o(.idata$3+0xc): undefined reference to `_libpostgres_a_iname'
fu04.o(.idata$3+0xc): undefined reference to `_libpostgres_a_iname'
fu05.o(.idata$3+0xc): undefined reference to `_libpostgres_a_iname'
fu06.o(.idata$3+0xc): undefined reference to `_libpostgres_a_iname'
fu07.o(.idata$3+0xc): more undefined references to `_libpostgres_a_iname' follow
nmth00.o(.idata$4+0x0): undefined reference to `__nm__TopMemoryContext'
nmth02.o(.idata$4+0x0): undefined reference to `__nm__SPI_tuptable'
nmth15.o(.idata$4+0x0): undefined reference to `__nm__SPI_processed'
nmth24.o(.idata$4+0x0): undefined reference to `__nm__Warn_restart'
nmth000128.o(.idata$4+0x0): undefined reference to `__nm__SPI_result'
nmth000133.o(.idata$4+0x0): undefined reference to `__nm__SPI_lastoid'

In src/pl/tcl/pltcl.c:
Permute the order of:
 #include "postgres.h"
 #include 
so as it appears as:
 #include 
 #include "postgres.h"

There is still some warnings, but it goes on:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations  -I../../../src/include   -c 
-o pltcl.o pltcl.c
In file included from ../../../src/include/pg_config.h:673,
 from ../../../src/include/c.h:53,
 from ../../../src/include/postgres.h:48,
 from pltcl.c:41:
../../../src/include/pg_config_os.h:26:1: warning: "DLLIMPORT" redefined
In file included from pltcl.c:39:
/usr/include/tcl.h:201:1: warning: this is the location of the previous definition
pltcl.c: In function `pltcl_init_interp':
pltcl.c:261: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:263: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:265: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:267: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:270: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:272: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:274: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c:276: warning: passing arg 3 of `Tcl_CreateCommand' from incompatible pointer 
type
pltcl.c: In function `pltcl_trigger_handler':
pltcl.c:818: warning: passing arg 4 of `Tcl_SplitList' from incompatible pointer type
pltcl.c: In function `pltcl_SPI_prepare':
pltcl.c:1745: warning: passing arg 4 of `Tcl_SplitList' from incompatible pointer type
pltcl.c: In function `pltcl_SPI_execp':
pltcl.c:2054: warning: passing arg 4 of `Tcl_SplitList' from incompatible pointer type

Reference: see also http://archives.postgresql.org/pgsql-cygwin/2003-01/msg00080.php

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1020: Timestamp representation printed by PostgreSQL are invalid

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1020
Logged by:  Sebastiano Vigna
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.4
Operating system:   Linux
Description:Timestamp representation printed by PostgreSQL are invalid
Details: 

create table test (t time);
select CURRENT_TIME;
   timetz

 16:42:11.183148+01
(1 row)
insert into test VALUES('16:42:11.183148+01');
ERROR:  Bad time external representation '16:42:11.183148+01'

This is nonsense: the representation returned by a SELECT  for a data type should be 
*VALID*, shouldn't it?

I'm trying to pre-compute the default values of a field using SELECT as above, but 
when I try to fill the field I get an error, as above.

Ciao,

seba

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1021: IDENT authorization doesn't work

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1021
Logged by:  alexeyof
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   FreeBSD 4.9-STABLE
Description:IDENT authorization doesn't work
Details: 

OS: FreeBSD 4.9-STABLE
PG: PostgreSQL 7.4 (installed from ports collection)

pg_hba.conf:

local template1 psql ident sameuser
local all   all  md5

(where pgsql is database owner)

When I try to start postgres, I get the following continuous error messages:

Dec 19 20:38:06 postgres[1435]: [2-1] FATAL:  invalid frontend message type 0
Dec 19 20:38:07 postgres[1439]: [2-1] FATAL:  invalid frontend message type 0
Dec 19 20:38:08 postgres[1443]: [2-1] FATAL:  invalid frontend message type 0
Dec 19 20:38:09 postgres[1447]: [2-1] FATAL:  invalid frontend message type 0
Dec 19 20:38:10 postgres[1451]: [2-1] FATAL:  invalid frontend message type 0

After a timeout it seems that postgres has started, I can even connect to 'template1', 
but when I try to execute any query, it shows the 'FATAL:  invalid frontend message 
type 0' error again and drops the connection.



---(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

[BUGS] BUG #1022: date calculation forces wrong type in function parameter and causes error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1022
Logged by:  Bruce Patin
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   FreeBSD 4.8-RELEASE
Description:date calculation forces wrong type in function parameter and 
causes error
Details: 

In PostgreSQL 7.4 only, a date type provided as a function parameter gets 
automatically typecast to 'timestamp without time zone' when calculations are 
performed on it.

In Pg 7.3 and before, I have successfully used a function with a date parameter such 
as this simplified version:

CREATE FUNCTION input_date(date) RETURNS INT AS 'SELECT 0;' LANGUAGE 'SQL';

Then, when I calculate a date during execution,
such as:

select input_date('now'::date+'5 years'::interval);

PostgreSQL 7.4 gives error:

ERROR:  function input_date(timestamp without time zone) does not exist

The same function works correctly in PostgreSQL 7.3 and before, and it also works even 
in 7.4 if I do not try to do date calculation, such as:

select input_date('now');


---(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

[BUGS] BUG #1024: Just Testing...

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1024
Logged by:  Dave Page

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   CYGWIN_NT-5.1 pc30 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown 
unknown 
Cygwin 

Description:Just Testing...

Details: 

#ifdef __LINUX__
{
wxLogNull noLog;
locale.AddCatalog(wxT("fileutils"));
}
#endif

if (langCount)
{
wxString *langNames=new wxString[langCount+1];
langNames[0] = _("Default");

for (langNo = 0; langNo < langCount ; langNo++)
{
langInfo = 
wxLocale::GetLanguageInfo(existingLangs.Item(langNo)); 
langNames[langNo+1] = wxT("(") + langInfo->CanonicalName + 
wxT(") ") 
+ existingLangNames.Item(langNo);
}


langNo = wxGetSingleChoiceIndex(_("Please choose user 
language:"), _("User language"),  
langCount+1, langNames);
if (langNo > 0)
(wxLanguage)wxLocale::GetLanguageInfo(existingLangs.Item(langNo-1))->Langua
langId = ge; 

delete[] langNames;
}
}

if (langId != wxLANGUAGE_UNKNOWN)
{
if (locale.Init(langId))
{
#ifdef __LINUX__
{
wxLogNull noLog;
locale.AddCatalog(wxT("fileutils"));
}
#endif


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1023: Just Testing...

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1023
Logged by:  Dave Page

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   CYGWIN_NT-5.1 pc30 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown 
unknown 
Cygwin 

Description:Just Testing...

Details: 

#ifdef __LINUX__
{
wxLogNull noLog;
locale.AddCatalog(wxT("fileutils"));
}
#endif

if (langCount)
{
wxString *langNames=new wxString[langCount+1];
langNames[0] = _("Default");

for (langNo = 0; langNo < langCount ; langNo++)
{
langInfo = 
wxLocale::GetLanguageInfo(existingLangs.Item(langNo)); 
langNames[langNo+1] = wxT("(") + langInfo->CanonicalName + 
wxT(") ") 
+ existingLangNames.Item(langNo);
}


langNo = wxGetSingleChoiceIndex(_("Please choose user 
language:"), _("User language"),  
langCount+1, langNames);
if (langNo > 0)
(wxLanguage)wxLocale::GetLanguageInfo(existingLangs.Item(langNo-1))->Langua
langId = ge; 

delete[] langNames;
}
}

if (langId != wxLANGUAGE_UNKNOWN)
{
if (locale.Init(langId))
{
#ifdef __LINUX__
{
wxLogNull noLog;
locale.AddCatalog(wxT("fileutils"));
}
#endif


---(end of broadcast)---
TIP 8: explain analyze is your friend

[BUGS] BUG #1025: current_time accepts 24:00:00

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1025
Logged by:  Rex Recio

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.3

Operating system:   Red Hat Linux 7.3

Description:current_time accepts 24:00:00

Details: 

I have a table containing 2 columns with default values of current_date and 
current_time.  When I don't fill in the values, the current_time default 
sometimes fill-in a value of 24:00:00 instead of wrapping it to 00:00:00.  
The other column with the current_date as default fills-in a value as if the 
time is 23:59:59.   




---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1026: org.apache.commons.dbcp.DbcpException: The connection attempt failed because failed getting backend

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1026
Logged by:  NASA

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.4

Operating system:   Solaris 9

Description:org.apache.commons.dbcp.DbcpException: The connection 
attempt failed because failed getting backend  

Details: 

We are trying to install DSPACE with POSTGRES.  When we run the ant 
fresh_install command we get the following error.  What could be causing a 
org.apache.commons.dbcp.DbcpException: The connection attempt failed because 
failed getting backend encoding? 

$ ant fresh_install
Buildfile: build.xml

update:

install_code:

setup_database:
 [java] 2003-12-23 14:09:48,719 INFO  
org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database 
 [java] 2003-12-23 14:09:50,143 FATAL 
org.dspace.storage.rdbms.InitializeDatabase @ Caught exception: 
 [java] org.apache.commons.dbcp.DbcpException: The connection attempt 
failed because failed getting backend encoding 
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(Dri
 [java] at verManagerConnectionFactory.java:101) 
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnec
 [java] at tionFactory.java:184) 
 [java] at 
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown Source) 
 [java] at 
org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:146) 
 [java] at 
java.sql.DriverManager.getConnection(DriverManager.java:512) 
 [java] at 
java.sql.DriverManager.getConnection(DriverManager.java:193) 
org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java
 [java] at :382) 
 [java] at 
org.dspace.storage.rdbms.DatabaseManager.loadSql(DatabaseManager.java:668) 
 [java] at 
org.dspace.storage.rdbms.InitializeDatabase.main(InitializeDatabase.java:76) 
 [java] Caused by: The connection attempt failed because failed getting 
backend encoding 
org.postgresql.jdbc1.AbstractJdbc1Connection.openConnection(AbstractJdbc1Co
 [java] at nnection.java:358) 
 [java] at org.postgresql.Driver.connect(Driver.java:122)
 [java] at 
java.sql.DriverManager.getConnection(DriverManager.java:512) 
 [java] at 
java.sql.DriverManager.getConnection(DriverManager.java:171) 
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(Dri
 [java] at verManagerConnectionFactory.java:95) 
 [java] ... 8 more

BUILD FAILED
file:/export/home/dspace-1.1.1-source/build.xml:220: Java returned: 1

Total time: 18 seconds


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1027: incorrect result from 'order by'

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1027
Logged by:  William H Copson

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   Redhat 7.2 (highly modified)

Description:incorrect result from 'order by'

Details: 

The following:

drop table tst;
create table tst (
name varchar(25));
insert into tst values ('LEE,ADAM');
insert into tst values ('LEEBERMAN,JOHN');
insert into tst values ('LEE,RALPH');
select name from tst order by name;

Produces the following output:

DROP TABLE
CREATE TABLE
INSERT 3307587 1
INSERT 3307588 1
INSERT 3307589 1
  name

 LEE,ADAM
 LEEBERMAN,JOHN
 LEE,RALPH
(3 rows)

Expected output:
  name

 LEE,ADAM
 LEE,RALPH
 LEEBERMAN,JOHN
(3 rows)

I have tried databases with SQL_ASCII, LATIN1 and LATIN2
encoding with the same result.
>From this small example and others involving an employee
table (80K+ records) it appears that the comma is being
parsed out prior to the sort (i.e. 'LEEB' sorts after
'LEEA' and before 'LEER').



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1028: order by problem

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1028
Logged by:  William H Copson

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Redhat 7.2 (highly modified)

Description:order by problem

Details: 

Sorry, in the previoius submission I forgot to change the
PostgreSQL version above. I have 7.4, not 7.5 Dev.

The following:

drop table tst;
create table tst (
name varchar(25));
insert into tst values ('LEE,ADAM');
insert into tst values ('LEEBERMAN,JOHN');
insert into tst values ('LEE,RALPH');
select name from tst order by name;

Produces the following output:

DROP TABLE
CREATE TABLE
INSERT 3307587 1
INSERT 3307588 1
INSERT 3307589 1
  name

 LEE,ADAM
 LEEBERM AN,JOHN
 LEE,RALPH
(3 rows)

Expected output:
  name

 LEE,ADAM
 LEE,RALPH
 LEEBERM AN,JOHN
(3 rows)

I have tried databases with SQL_ASCII, LATIN1 and LATIN2
encoding with the same result. From this small example
and others involving an employee table (80K+ records) it appears that the 
comma is being parsed out prior to the 
sort (i.e. 'LEEB' sorts after 'LEEA' and before 'LEER').



---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1029: Configuration parameter problem

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1029
Logged by:  Ranjan

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Configuration parameter problem

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1030: Configuration parameter problem

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1030
Logged by:  Ranjan

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Configuration parameter problem

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1031: Problem in configuring postgresql file

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1031
Logged by:  ALOK

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Problem in configuring postgresql file

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1032: Problem in configuring postgresql file

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1032
Logged by:  ALOK

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Problem in configuring postgresql file

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1033: Problem in configuring postgresql file

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1033
Logged by:  ALOK

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Problem in configuring postgresql file

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1034: Problem in configuring postgresql file

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1034
Logged by:  ALOK

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Problem in configuring postgresql file

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1035: Problem in configuring postgresql file

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1035
Logged by:  ALOK

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Redhat 9

Description:Problem in configuring postgresql file

Details: 

Respected Sir,
 I am working on the opennms project for the last 2 months , but have 
been facing problems with the configuration of the postgresql and 
postmaster. 
 I am appending my postgresql file below:
Please reply what are the flaws in this file and which other lines are to be 
uncommented . 

Connection Parameters
#
tcpip_socket = true
#ssl = false

max_connections = 256
#superuser_reserved_connections = 2

port = 5432 
hostname_lookup = true
#show_source_port = false

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777 # octal

virtual_host = 'localhost'

#krb_server_keyfile = ''


#
#   Shared Memory Size
#
shared_buffers = 1024   # min max_connections*2 or 16, 8KB each
#max_fsm_relations = 1000   # min 10, fsm is free space map, ~40 bytes
#max_fsm_pages = 1  # min 1000, fsm is free space map, ~6 bytes
#max_locks_per_transaction = 64 # min 10
#wal_buffers = 8# min 4, typically 8KB each

#
#   Non-shared Memory Sizes
#
#sort_mem = 1024# min 64, size in KB
#vacuum_mem = 8192  # min 1024, size in KB


#
#   Write-ahead log (WAL)
#
#checkpoint_segments = 3# in logfile segments, min 1, 16MB each
#checkpoint_timeout = 300   # range 30-3600, in seconds
#
#commit_delay = 0   # range 0-10, in microseconds
#commit_siblings = 5# range 1-1000
#
#fsync = true
#wal_sync_method = fsync# the default varies across platforms:
#   # fsync, fdatasync, open_sync, or open_datasync
#wal_debug = 0  # range 0-16


#
#   Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#effective_cache_size = 1000# typically 8KB each
#random_page_cost = 4   # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01  # (same)
#cpu_index_tuple_cost = 0.001   # (same)
#cpu_operator_cost = 0.0025 # (same)

#default_statistics_target = 10 # range 1-1000

#
#   GEQO Optimizer Parameters
#
#geqo = true
#geqo_selection_bias = 2.0  # range 1.5-2.0
#geqo_threshold = 11
#geqo_pool_size = 0 # default based on tables in statement, 
# range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1  # auto-compute seed


#
#   Message display
#
#server_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   info, notice, warning, error, log, fatal,
#   panic
#client_min_messages = notice   # Values, in order of decreasing detail:
#   debug5, debug4, debug3, debug2, debug1,
#   log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing severity:
 #   debug5, debug4, debug3, debug2, debug1,
 #   info, notice, warning, error, panic(off)

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#explain_pretty_print = true

# requires USE_ASSERT_CHECKING
#debug_assertions = true


#
#   Syslog
#
#syslog = 0 # range 0-2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'


#
#   Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_statement_stats = false

# requires BTREE_BUILD_STATS
#show_btree_build_stats = false


#
#   Access statistics collection
#
#stats_start_collector = true
#stats_reset_on_server_start = true
#stats_command_string = false
#stats_row_level = false
#stats_block_level = false


#
#   Lock Tracing
#
#trace_notify = false

# requires LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0


#
#   Misc
#
#autocommit = true
#dynamic_library_path = '$libdir'
#search_path = '$user,public'
#datestyle = 'iso, us'
#timezone = unknown # actually, defaults to TZ environment setting
#australian_timezones = false
#client_encoding = sql_ascii# actually, defaults to database encoding
#authentication_timeout = 60# 1-600, in seconds
#deadloc

[BUGS] BUG #1036: programm result

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1036
Logged by:  ravishankar

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:programm  result

Details: 

actually a programm can not give the perfect result


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1037: internal error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1037
Logged by:  prakash

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:internal error

Details: 

 programm generates internal error.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1038: Upon reload of data to install of v7.41 defaults for fields get screwed up

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1038
Logged by:  Stuart Green

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Redhat Linux

Description:Upon reload of data to install of v7.41 defaults for 
fields get screwed up 

Details: 

I have a table with a field creationdatetime timestamp default 'now'

I just dumped that data from V7.3.4 and reloaded into V7.4.1 and the 'now' 
part of the default got translated to the date and time that the data was 
reloaded, instead of maintaining the now. 


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1039: programm compilation

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1039
Logged by:  prakash

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:programm compilation

Details: 

A programm compiled with invalid outputs.


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

[BUGS] BUG #1040: runtime error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1040
Logged by:  raja

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:runtime error

Details: 

runtime error can be occured during  programm compilation


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1041: runtime error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1041
Logged by:  smitha

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:runtime error

Details: 

runtime error occured while compiling the program


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1042: runtime error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1042
Logged by:  smitha

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:runtime error

Details: 

Runtime error occurs while compiling the program


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1043: PSQL.exe

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1043
Logged by:  Serkan SUNEL

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Windows XP

Description:PSQL.exe 

Details: 

Problem occur while restoring the database from the backup file if i use 
psql -f c:\cygwin\bin\dump_file_name -d mydatabase_name
This is not working properly...this command only create tables and 
stops...does not insert the records... 

I think the file path creates this problem . Because 
psql -f dump_file_name -d mydatabase_name is working very good..




---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1044: snprintf() shipped with PostgreSQL is not thread safe

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1044
Logged by:  Denis Stepanov

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Any OS lacking proper snprintf()

Description:snprintf() shipped with PostgreSQL is not thread safe

Details: 

Some OSes lack proper snprintf()/vsnprintf() fuctions so PostgreSQL includes 
its own version (src/port/snprintf.c) during building. Unfortunately, this 
version of snprintf() is not reentrant (it uses global vars to keep internal 
state), so for example running libpq-based concurrent applications (threads) 
causes libpq fuctions to fail sometimes. The suggestion is to remove globals 
usage in src/port/snprintf.c. I am attaching here a sample patch for your 
review. Thanks. 

--- postgresql-7.4.1/src/port/snprintf.cThu Jul 18 11:13:59 2002
+++ postgresql-7.4.1.fixed/src/port/snprintf.c  Thu Jan  8 13:23:47 2004
@@ -67,6 +67,9 @@
  * Sigh.  This sort of thing is always nasty do deal with. Note that
  * the version here does not include floating point. (now it does ... tgl)
  *
+ * Denis Stepanov Thu Jan  8 13:01:01 NOVT 2004
+ * Made functions reentrant (thread safe).
+ *
  * snprintf() is used instead of sprintf() as it does limit checks
  * for string length.  This covers a nasty loophole.
  *
@@ -75,12 +78,18 @@
  **/
 
 /*static char _id[] = "$Id: snprintf.c,v 1.1 2002/07/18 04:13:59 momjian 
Exp $";*/ 
-static char *end;
-static int SnprfOverflow;
+
+typedef struct _vsnprintf_data 
+{
+   int SnprfOverflow;
+   char *end;
+   char *output;
+
+} vsnprintf_data;
 
 intsnprintf(char *str, size_t count, const char *fmt,...);
 intvsnprintf(char *str, size_t count, const char *fmt, va_list 
args);
-static void dopr(char *buffer, const char *format, va_list args);
+static void dopr(char *buffer, const char *format, va_list args, 
vsnprintf_data *vsnpd); 
 
 int
 snprintf(char *str, size_t count, const char *fmt,...)
@@ -98,12 +107,14 @@
 int
 vsnprintf(char *str, size_t count, const char *fmt, va_list args)
 {
+   vsnprintf_data vsnpd;
+   
str[0] = '\0';
-   end = str + count - 1;
-   SnprfOverflow = 0;
-   dopr(str, fmt, args);
+   vsnpd.end = str + count - 1;
+   vsnpd.SnprfOverflow = 0;
+   dopr(str, fmt, args, &vsnpd);
if (count > 0)
-   end[0] = '\0';
+   vsnpd.end[0] = '\0';
return strlen(str);
 }
 
@@ -111,17 +122,16 @@
  * dopr(): poor man's version of doprintf
  */
 
-static void fmtstr(char *value, int ljust, int len, int zpad, int 
maxwidth); 
-static void fmtnum(long_long value, int base, int dosign, int ljust, int 
len, int zpad); 
-static void fmtfloat(double value, char type, int ljust, int len, int 
precision, int pointflag); 
-static void dostr(char *str, int cut);
-static void dopr_outch(int c);
+static void fmtstr(char *value, int ljust, int len, int zpad, int maxwidth, 
vsnprintf_data *vsnpd); 
+static void fmtnum(long_long value, int base, int dosign, int ljust, int 
len, int zpad, vsnprintf_data *vsnpd); 
+static void fmtfloat(double value, char type, int ljust, int len, int 
precision, int pointflag, vsnprintf_data *vsnpd); 
+static void dostr(char *str, int cut, vsnprintf_data *vsnpd);
+static void dopr_outch(int c, vsnprintf_data *vsnpd);
 
-static char *output;
 
 
 static void
-dopr(char *buffer, const char *format, va_list args)
+dopr(char *buffer, const char *format, va_list args, vsnprintf_data *vsnpd)
 {
int ch;
long_long   value;
@@ -135,7 +145,7 @@
int len;
int zpad;
 
-   output = buffer;
+   vsnpd->output = buffer;
while ((ch = *format++))
{
switch (ch)
@@ -148,8 +158,8 @@
switch (ch)
{
case 0:
-   dostr("**end of format**", 0);
-   *output = '\0';
+   dostr("**end of format**", 0, vsnpd);
+   *vsnpd->output = '\0';
return;
case '-':
ljust = 1;
@@ -188,7 +198,7 @@
goto nextch;
case 'u':
case 'U':
-   /* 
fmtnum(value,base,dosign,ljust,len,zpad) */
+ 

[BUGS] BUG #1045: hostname lookup in psql or libpg.sl does work

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1045
Logged by:  Keith Halewood

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   HP-UX 11i

Description:hostname lookup in psql or libpg.sl does work

Details: 

psql (and libpg.sl via the DBI and DBD::Pg interface) report:

psql: could not translate host name "ysolde" to address: host nor service 
provided, or not known 

despite ysolde, in this case, being available via the DNS and both nslookup 
and dig (and all the other clients) correctly resolving names. 

If 'ysolde' and its address are placed in the system's /etc/hosts file, psql 
(and libpq.sl) is able to resolve an address and connect. 


---(end of broadcast)---
TIP 8: explain analyze is your friend

[BUGS] BUG #1046: UNIQUE INDEX BUG

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1046
Logged by:  Alfonso Baqueiro

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.2

Operating system:   Linux Redhat 9.0

Description:UNIQUE INDEX BUG

Details: 

create table pru(
  id integer not null primary key,
  login varchar(10) unique not null
);

then when inserting values it says á = é = í = ó = ú
(confuses different acuted vowels as if they were the same thing)

insert into pru (0, 'á');
-- no problem

But the error shows when trying the next:
insert into pru (1, 'é');
-- ERROR: cannot insert a duplicate key into unique index ...

Is a horrible bug that stops my migration from Centura SQLBase to PostgreSQL


---(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

[BUGS] BUG #1047: sdav

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1047
Logged by:  sv dzsvsf

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   linux

Description:sdav

Details: 

sfvszzcsv   xf ss


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1048: error connection to dbms from java app server

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1048
Logged by:  Christopher Conlon

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   FreeBSD 5.1

Description:error connection to dbms from java app server

Details: 

I get an error from Jboss app server when trying to connect to postgresql. I 
am using the jdbc driver that was built with --with-java.  This same bug 
showed up when  I tried to use Postgres 7.3.4. 

17:40:30,661 WARN  [JBossManagedConnectionPool] Throwable while attempting 
to get a new connection: 
org.jboss.resource.JBossResourceException: Could not create connection; - 
nested throwable: (java.sql.SQLException: ERROR:  unrecognized configuration 
 parameter "xactisolevel"
)
org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createM
at anagedConnection(LocalManagedConnectionFactory.java:160) 
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createCo
at nnectionEventListener(InternalManagedConnectionPool.java:477) 
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConne
at ction(InternalManagedConnectionPool.java:213) 
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.ge
at tConnection(JBossManagedConnectionPool.java:496) 
org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConne
at ction(BaseConnectionManager2.java:425) 
org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnecti
at on(TxConnectionManager.java:318) 
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnect
at ion(BaseConnectionManager2.java:477) 
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManag
at erProxy.allocateConnection(BaseConnectionManager2.java:814) 
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperData
at Source.java:102) 
at truss.user.UserBean.makeConnection(UserBean.java:142)
at truss.user.UserBean.insertRow(UserBean.java:162)
at truss.user.UserBean.ejbCreate(UserBean.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
at 9) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
at l.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324)
org.jboss.ejb.plugins.BMPPersistenceManager.createEntity(BMPPersistenceMana
at ger.java:196) 
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.createEnti
at ty(CachedConnectionInterceptor.java:269) 
at 
org.jboss.ejb.EntityContainer.createHome(EntityContainer.java:737) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
at 9) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
at l.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324)
org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContain
at er.java:1043) 
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySyn
at chronizationInterceptor.java:197) 
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome
at (CachedConnectionInterceptor.java:214) 
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.ja
at va:88) 
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceIn
at terceptor.java:89) 
org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockIntercepto
at r.java:61) 
org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationIn
at terceptor.java:28) 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxIntercepto
at r.java:88) 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT
at .java:267) 
at 
org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:98) 
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.ja
at va:92) 
at 
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120) 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactory
at FinderInterceptor.java:93) 
at 
org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:483) 
at org.jboss.ejb.Container.invoke(Container.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
at 9) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
at l.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324)
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispa

[BUGS] BUG #1049: Invalid SQL Executed as JDBC Prepared Statement still executes embedded SQL

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1049
Logged by:  Tom Hargrave

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.2

Operating system:   Linux

Description:Invalid SQL Executed as JDBC Prepared Statement still 
executes embedded SQL 

Details: 

If a piece of SQL is executed in a JDBC prepared statement that includes a 
semicolon and a valid piece of SQL, then the embedded valid piece of SQL 
still executes even though the overall statement is invalid. 

Example: 

select c1 from t1 order by;drop t2; c1

This causes security issues if the SQL is constructed from a web page that 
inputs strings that are used to construct a statement, since a hacker can 
embed SQL within a single field that executes regardless of the overall 
statement being invalid. 

See article:

http://www.computerweekly.com/articles/article.asp?liArticleID=127470&liFla
vourID=1 


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1050: cannot restore db at postgresql 7.4.1

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1050
Logged by:  Taku YASUI

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Debian GNU/Linux

Description:cannot restore db at postgresql 7.4.1

Details: 

I tried to upgrade postgresql from 7.1.2(other host) to
7.4.1(localhost).  However an error occured and failed
restore.

I tried following steps.

   % pg_dump --version
   pg_dump (PostgreSQL) 7.4.1
   % pg_dump -b -Fc -h host -U user dbname -f dbname.dump
   % pg_restore -v -d dbname dbname.dump
   :
   pg_restore: restoring data for table "table_name"
   pg_restore: ERROR:  invalid input syntax for integer: "
   "
   CONTEXT:  COPY table_name, line 2, column column_name: "
   "
   pg_restore: [archiver (db)] error returned by PQendcopy
   pg_restore: *** aborted because of error

This error does not occur 7.3.4.  I found
a modification from 7.3 to 7.4 to cause this problem.
The release notes of 7.4 saids:

   COPY now can process files that use carriage-return or 
carriage-return/line-feed end-of-line sequences. Literal carriage-returns 
and line-feeds are no longer accepted in data values; use \r and \n instead. 

When I tried to use '-d' option to run pg_dump,
pg_restore completed.  Therefore, I think this
modification causes the problem.

I think this is bug and pg_dump/pg_restore should
be fixed to keep with this modification.



---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1051: Cannot remove groups

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1051
Logged by:  Jari Aalto

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   W2k SP4 / Cygwin

Description:Cannot remove groups

Details: 

It is impossible to give details how this error
is triggered, because I do not know enough details
of PG's internals. I happened to crete databases, user, groups and then 
deleting them in random order and now the groups are totally inaccessible in 
all ways. 


The problem is that the admin files say that I have 
groups. But they cannot be removed. And because
they cannot be removed or recreated, I cannot
grant anything to groups.

I tried to install all from  fresh with:

[EMAIL PROTECTED]:/usr/share/postgresql# rm -rf data/  
   [EMAIL PROTECTED]:/usr/share/postgresql# LC_ALL=C initdb -D 
/usr/share/postgresql/data 



But that dind't affect the groups or users. This was verified by running 
select from pg_group and pg_users immedately after total recreation. 

See logs below. Please let me know how to preceed
and help to find more details for you.

Jari



[EMAIL PROTECTED]:/usr/share/postgresql# rm -rf data/  
   [EMAIL PROTECTED]:/usr/share/postgresql# LC_ALL=C initdb -D 
/usr/share/postgresql/ 
data
The files belonging to this database system will be owned by user "root".
This user must also own the server process.

The database cluster will be initialized with locale C.

creating directory /usr/share/postgresql/data... ok
creating directory /usr/share/postgresql/data/base... ok
creating directory /usr/share/postgresql/data/global... ok
creating directory /usr/share/postgresql/data/pg_xlog... ok
creating directory /usr/share/postgresql/data/pg_clog... ok
selecting default max_connections... 100
selecting default shared_buffers... 1000
creating configuration files... ok
creating template1 database in /usr/share/postgresql/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ok
setting privileges on built-in objects... ok
creating information schema... ok
vacuuming database template1... ok
copying template1 to template0... ok

Success. You can now start the database server using:

/bin/postmaster -D /usr/share/postgresql/data
or
/bin/pg_ctl -D /usr/share/postgresql/data -l logfile start

[EMAIL PROTECTED]:/usr/share/postgresql# psql -d template1 
   Welcome to psql 7.4, the PostgreSQL interactive terminal. 

Type:  \copyright for distribution terms
   \h for help with SQL commands
   \? for help on internal slash commands
   \g or terminate with semicolon to execute query
   \q to quit

template1=# SELECT  groname
template1-# , grosysid
template1-# , grolist   AS "Users in group"
template1-# FROMpg_group
template1-# ;
 groname | grosysid | Users in group 
-+--+
 admin   |  112 | 
 root|  113 | 
 reader  |  110 | {106}
 users   |  111 | {107,108}
(4 rows)

template1=# SELECT  usename
template1-# , usesysid
template1-# , usecreatedb   AS "create db"
template1-# , usesuper  AS "root"
template1-# , usecatupd AS "sys catalogs"
template1-# FROMpg_user
template1-# ;
 usename | usesysid | create db | root | sys catalogs 
-+--+---+--+--
 root|1 | t | t| t
 scott   |  106 | f | f| f
 test|  107 | f | f| f
 king|  108 | f | f| f
(4 rows)


template1=# drop group admin;
ERROR:  group "admin" does not exist
template1=# drop group root;
ERROR:  group "root" does not exist
template1=# drop group reader;
ERROR:  group "reader" does not exist
template1=# drop group users;
ERROR:  group "users" does not exist
template1=# 


[EMAIL PROTECTED]:/usr/share/postgresql# ls -la
total 22134
drwxr-xr-x5 root Administ0 Jan 17  2002 .
drwxr-xr-x   67 root Administ0 Feb 10  2001 ..
drwxr-xr-x2 root Administ0 Nov 26 22:49 contrib
-rw-r--r--1 root Administ38974 Nov 19 18:21 
conversion_create.sql 
drwxr-xr-x6 root Administ0 Jan 16 20:22 data
-rw-r--r--1 root Administ65566 Nov 19 18:21 
information_schema.sql 
drwxr-xr-x2 root Administ0 Nov 26 22:49 java
-rw-r--r--1 root Administ0 May 18  2003 
list.emacs-bbdb.spool 
-rw-r--r--1 root Administ  7012794 May 18  2003 
list.emacs-devel.spool 
-rw-r--r--1 root Administ  7168836 May 18  2003 
list.emacs-ding.spool 
-rw-r--r--1 root Administ0 May 18  2003 list.

[BUGS] BUG #1052: Problem while Installation of postgreSQL

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1052
Logged by:  Nilesh Ghone

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.4

Operating system:   Windows 2000 Professional

Description:Problem while Installation of postgreSQL

Details: 

Dear Sir/Madam,
For professional s/w development, I want to use PostgreSQL. According to 
documentation (FAQ_MSWIN), I have installed cygwin on my PC. After 
installation I have started ipc-daemon2 by  command on cygwin 
shell. it worked fine. Then used initdb command to create new database 
cluster using   cygcrypt-0.dll not in path.
2)The program
/usr/bin/postgres
needed by initdb does not belong to PostgreSQL version 7.4.1, or
there may be a configuration problem.
 
Please suggest any solution. Thank you.
 
Regards,
Nilesh
 



---(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

[BUGS] BUG #1053: Configuration should be in /etc/postgres

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1053
Logged by:  Jari 

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   W2k/Cygwin

Description:Configuration should be in /etc/postgres

Details: 

It would be better if postgres kept the configurations 
files in standard /etc location. Like under
/etc/postgres

Right now the files are under the DATA directory:

  postgresql.conf
  pg_hba.conf

Debian does this, so perhaps that could be used in
the core distribution as well?




---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1054: inefficient compression of doco html files

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1054
Logged by:  Jim Donovan

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   linux

Description:inefficient compression of doco html files

Details: 

In the bzip2 tarballs, the doco HTML files are
first compressed with gzip.
This is inefficient. It would be better to make
the first compression a bzip2. A subsequent hit
with bzip2 cannot undo the less dense compression
attained with gzip.
It would be better still not to first compress; the
subsequent hit with bzip2 would be ample.


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1055: no keys in inherited table with primary key when inserting into inheriting table

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1055
Logged by:  Agri

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   PC-linux-gnu

Description:no keys in inherited table with primary key when 
inserting into inheriting table 

Details: 

let me desribe a bug in the term of sql commands:
create table first (id int primary key );
create table second (f2 int) inherits (first);
create table third (ref_id int);
alter table third add constraint third_ref_first foreign key (ref_id) 
references first; 
insert into second (id, f2) values (1, 1);

and at last a bug insert:
insert into third (ref_id) values (1);
results in:
ERROR:  insert or update on table "third" violates foreign key constraint 
"third_ref_first" 

if i get a select:
select * from first;
 id 

  1
(1 row)

bug is: values are not added into primary key of the inherited table when 
records are inserted into the inheriting table 


---(end of broadcast)---
TIP 8: explain analyze is your friend

[BUGS] BUG #1056: ecpg ignores WHENEVER NOT FOUND

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1056
Logged by:  Wes

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Redhat Linux 7.3

Description:ecpg ignores WHENEVER NOT FOUND

Details: 

This problem occurs with both 7.4 and 7.4.1.  The problem does not occur at 
7.3.4. 

I have a statement in my program such as:

 EXEC SQL WHENEVER NOT FOUND GOTO nextvalError;

The C code generated by ecpg at 7.4 and 7.4.1 is missing the statement:

 if (sqlca.sqlcode == ECPG_NOT_FOUND) goto nextvalError;

My workaround is to manually insert this code in my program.


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1058: unexpected output when using timezone() and to_char()

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1058
Logged by:  Blake Crosby

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.2

Operating system:   FreeBSD 5.1-RELEASE-p11

Description:unexpected output when using timezone() and to_char()

Details: 

select to_char(CURRENT_TIMESTAMP,'Day Mon DD  HH24:MI:SS TZ');

returns:

  to_char   

 Wednesday Jan 21 2004 10:02:11 EST


however, 

select to_char(timezone('PST',CURRENT_TIMESTAMP),' Day Mon DD  
HH24:MI:SS TZ'); 

returns:

 to_char  
--
  Wednesday Jan 21 2004 07:07:44 


Notice the Time zone field (specified by 'TZ' in the to_char) is missing 
from the output. 


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1059: Second Call of a PGSQL-function fails

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1059
Logged by:  Wilhelm

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux

Description:Second Call of a PGSQL-function fails 

Details: 

-- The Source:

-- Init Stuff
DROP FUNCTION plpgsql_call_handler () CASCADE;
CREATE FUNCTION plpgsql_call_handler () RETURNS LANGUAGE_HANDLER AS
'$libdir/plpgsql' LANGUAGE C;

CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql
HANDLER plpgsql_call_handler;

-- The function

CREATE FUNCTION f (INTEGER) RETURNS INTEGER
AS '
BEGIN
  CREATE TABLE test ( x INTEGER );

  -- Without this insert, everything works well...
  INSERT INTO test VALUES (1);

  DROP TABLE test CASCADE;

  RETURN 0;
END;
' LANGUAGE 'plpgsql';

-- That works.
SELECT f(1);

-- Second Call fails.
SELECT f(1);

-- Thanks in advance, Wilhelm



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1060: psql encoding bug : sjis

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1060
Logged by:  Hitoshi Gosen

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   linux 2.4.9

Description:psql encoding bug : sjis

Details: 

version 7.4.1

installation steps:

./configure
 gmake
 su
 gmake install
 adduser postgres
 mkdir /usr/local/pgsql/data
 chown postgres /usr/local/pgsql/data
 su - postgres
 /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
 /usr/local/pgsql/bin/postmaster - D usr/local/pgsql/data >logfile 2>&1 &
 /usr/local/pgsql/bin/createdb test1

client:
 /usr/local/pgsql/bin/psql test1
 \encoding sjis
 create table テスト情報(テスト character(4));
 \d
-

the last command \d shows me a different name for the table. 
I cannot access the table.





---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1061: message type 0x49 arrived from server while idle

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1061
Logged by:  Robert Creager

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux Mandrake 9.2 2.4.22 SMP

Description:message type 0x49 arrived from server while idle

Details: 


The problem is not occuring very often, 3 times in a week.  A  is 
showing the connection "idle in transaction".  pg_autovacuum is running. 

This is a new install on a new dual Xenon machine.  The process which 
received the message is running on Solaris/Perl 5.6.1 using DBI 1.30 and 
DBD::Pg 1.22. 

The PGSQL version on Solaris is 7.3.3, but that shouldn't matter?

Compiled from source:
PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.1 
(Mandrake Linux 9.2 3.3.1-2mdk) 




---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1062: socket error

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1062
Logged by:  forty

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   windows me

Description:socket error

Details: 



PSQL.EXE: could not connect to server: Socket error, no 
description available (0X2740) 
Is the server running on host localhost and accepting 
TCP/IP connection on port 5432? 


---(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

[BUGS] BUG #1063: tcp/ip

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1063
Logged by:  forty

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   windows me

Description:tcp/ip

Details: 



PSQL.EXE: could not connect to server: Socket error, no 
description available (0X2740) 
Is the server running on host localhost and accepting 
TCP/IP connection on port 5432? 


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1064: work with temporary table in plpgsql function

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1064
Logged by:  Sergey

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   FreeBSD

Description:work with temporary table in plpgsql function

Details: 

If a followed function is called more once inside one session, then occured 
this error: 

ERROR:  relation with OID 19990 does not exist
CONTEXT:  PL/pgSQL function "test_temp" line 3 at SQL statement


TEST FUNCTION:

CREATE OR REPLACE FUNCTION public.test_temp()
  RETURNS int4 AS
'begin
  create temporary table itable(id int4, name varchar(100));
  insert into itable values(1, \'test\');
  drop table itable;

  return 0;
end;
'
  LANGUAGE 'plpgsql' VOLATILE;



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1065: JDBC DataSource Serializability

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1065
Logged by:  R. Lemos

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux

Description:JDBC DataSource Serializability

Details: 

The JDBC2 pooled datasource(org.postgresql.jdbc2.optional.ConnectionPool), 
although implements java.io.Serializable, cannot be correctly serialized. 
Its superclass does not implement java.io.Serializable and have important 
fields marked as private. 

Either should the superclass be Serializable or its fields non-private 
(protected, friend or public). 

To reproduce the issue just create and setup a ConnectionPool, serialize and 
desserialize it (ByteArray*Stream will do). The new object doesn't have the 
properties correctly set. 

This may apply to other DataSource implementations (JDBC3 and non-pooled).

PS: I could have corrected this and submitted the patch, but I don't know 
why are those properties private nor why isn't the superclass Serializable, 
so I could not preview the impact those changes would make. 


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1066: avg(age()) results months with more than 30 days

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1066
Logged by:  Beda Szukics

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.4

Operating system:   linux

Description:avg(age()) results months with more than 30 days

Details: 

Hello all

When I try to calculate the average age of the following birthdates I get
months with more than 30 days. Is this a bug?

I use version 7.3.4

These are the birthdates:


kongregation=> SELECT geb_dat FROM personen;
  geb_dat

 20.12.1946
 29.01.1948
 21.03.1933
 07.01.1954
 22.08.1959
 07.07.1913
 30.11.1922
 29.08.1925
 07.01.1927
 06.07.1928
 25.09.1928
 23.05.1929
 25.04.1930
 27.03.1933
 21.12.1933
 28.03.1937
 03.02.1940
 13.12.1941
 13.02.1942
 30.04.1937
 25.08.1943
 03.06.1964
 26.01.1956
 04.11.1957
 27.12.1961
 22.03.1911
 30.11.1918
 02.05.1957
 08.03.1925
(29 rows)



Today (20.1.2004 german style) I get the answer:

kongregation=> SELECT AVG(AGE(geb_dat)) FROM personen ;
avg

 @ 65 years 9 mons 4 days 0.00 secs
(1 row)


Yesterday and the day before yesterday I got:

kongregation=> SELECT AVG(AGE('19.01.2004',geb_dat)) FROM personen ;
 avg
--
 @ 65 years 8 mons 32 days 2 hours 28 mins 57.93 secs
(1 row)

kongregation=> SELECT AVG(AGE('20.01.2004',geb_dat)) FROM personen ;
 avg
-
 @ 65 years 8 mons 33 days 1 hour 39 mins 18.62 secs
(1 row)


BTW: I think having the result with years and days only would be a better
answer, what kind of months are counted in the present form?

Greetings   Beda



---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1067: typo in config template

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1067
Logged by:  Jörn Clausen

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   OSF1/Tru64 Unix

Description:typo in config template

Details: 

Hi!

postgresql-7.4.1/src/template/osf should be changed to

   THREAD_LIBS="-lpthread"

The "l" is missing.



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1068: arch dependant header files

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1068
Logged by:  Jörn Clausen

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   various

Description:arch dependant header files

Details: 

Hi!

The header files pg_config.h, pg_config_os.h and probably
pg_config_manual.h contain architecture dependant information. They should 
not be installed in .../include, 
as this directory is often shared across architectures.

I moved them to .../lib/include and created sym-links from the include 
directory. This should IMHO be automated by the Makefile(s). 



---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1069: functions "lower()" and "upper()" not characterset-aware

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1069
Logged by:  Interzone

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux 2.4.24

Description:functions "lower()" and "upper()" not characterset-aware

Details: 

the functions "lower()" and "upper()" do not seem to work correctly with 
ISO_8859_7 values 

Test case:
CREATE DATABASE mediagrk WITH TEMPLATE = template0 ENCODING = 'ISO_8859_7';
CREATE TABLE test1 (
   code serial NOT NULL,
   compname character varying(100) NOT NULL
);
INSERT INTO test1 VALUES (1, 'ÅËËÇÍÉÊÁ');
SELECT lower(compname) from test1;

if there is a problem (there might be) with the greek characters above, just 
remember that this is a iso-8859-7 encoded text (and I changed the encoding 
of the form-page to iso-8859-7 before sending). 



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1070: Postgres restarts OS

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1070
Logged by:  Piotr Mysliwiec

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.2.1

Operating system:   Debian woody

Description:Postgres restarts OS

Details: 

I have trouble with stability my system.

postgres make restart server sometimes 3 times in one hour day. Next two-7 
days i have no trouble. 
regards 


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1071: -fPIC needed for plperl & amd64

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1071
Logged by:  Palle Girgensohn

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   FreeBSD

Description:-fPIC needed for plperl & amd64

Details: 

Hi,

It seems that in order to build plperl on amd64, -fPIC is needed in CFLAGS.

Here's a trivial patch that fixes this for FreeBSD. It also adds the 
possibility to link plperl even if there is no shared libperl.so, only a 
static libperl.a. On FreeBSD, the perl ports are usually built with 
libperl.a only. 

--- src/makefiles/Makefile.freebsd.orig Wed Aug 29 21:14:40 2001
+++ src/makefiles/Makefile.freebsd  Sat Jan 31 17:51:25 2004
@@ -7,7 +7,7 @@
 endif
 
 DLSUFFIX = .so
-CFLAGS_SL = -fpic -DPIC
+CFLAGS_SL = -fPIC -DPIC
 
 %.so: %.o
 ifdef ELF_SYSTEM
@@ -23,3 +23,5 @@
 endif
 
 sqlmansect = 7
+
+allow_nonpic_in_shlib = yes



---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[BUGS] BUG #1072: "$libdir/ascii_and_mic": No such file or directory

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1072
Logged by:  Thomas Borg Salling

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Red Hat Linux (2.4.20-20.7)

Description:"$libdir/ascii_and_mic": No such file or directory

Details: 

I have downloaded and built Postgres 7.4.1:

as user 'tbs':
./configure --prefix=/opt/postgres-7.4.1/ --with-perl --enable-thread-safety
make
make check

as user 'root':
make install
mkdir /data/postgres
chown -R postgres /opt/postgres-7.4.1
chgrp -R postgres /opt/postgres-7.4.1
chown -R postgres /data/postgres
chgrp -R postgres /data/postgres

as user 'postgres':
[EMAIL PROTECTED] postgres]$ /opt/postgres-7.4.1/bin/initdb -D 
/data/postgres/ 
The files belonging to this database system will be owned by user 
"postgres". 
This user must also own the server process.

The database cluster will be initialized with locale en_US.iso885915.

fixing permissions on existing directory /data/postgres/... ok
creating directory /data/postgres//base... ok
creating directory /data/postgres//global... ok
creating directory /data/postgres//pg_xlog... ok
creating directory /data/postgres//pg_clog... ok
selecting default max_connections... 100
selecting default shared_buffers... 1000
creating configuration files... ok
creating template1 database in /data/postgres//base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ERROR:  could not access file 
"$libdir/ascii_and_mic": No such file or directory 

initdb: failed


Why does this fail? What can I do to resolve it?

Thanks in advance!

/Thomas.



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1073: JDBC "time with time zone"

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1073
Logged by:  Bob Messenger

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   Linux

Description:JDBC "time with time zone"

Details: 

create table a(b time with time zone);

insert into a values ('00:00:00');

import java.sql.*;

public class JDBC
{
public JDBC()
throws Exception
{
Class.forName("org.postgresql.Driver");
DriverManager.setLogStream(System.out);
Connection db = 
DriverManager.getConnection("jdbc:postgresql://blah/blah?loglevel=3", 
"postgres", null); 

Statement st = db.createStatement();
ResultSet rs = st.executeQuery("SELECT b FROM a");
while (rs.next())
{
System.out.println(rs.getString(1));
System.out.println(rs.getTimestamp(1));
}
rs.close();
st.close();
db.close();
}

public final static void main(String args[])
throws Exception
{
new JDBC();
}
}

getConnection returning 
driver[className=org.postgresql.Driver,[EMAIL PROTECTED] 
00:00:00+00
Exception in thread "main" org.postgresql.util.PSQLException: Bad Timestamp 
Format at 2 in 00:00:00+00 
org.postgresql.jdbc1.AbstractJdbc1ResultSet.toTimestamp(AbstractJdbc1Result
at Set.java:1183) 
org.postgresql.jdbc1.AbstractJdbc1ResultSet.getTimestamp(AbstractJdbc1Resul
at tSet.java:376) 
at JDBC.(JDBC.java:17)
at JDBC.main(JDBC.java:27)



---(end of broadcast)---
TIP 8: explain analyze is your friend

[BUGS] BUG #1074: postgresql crashes

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1074
Logged by:  Neeraj K Sharma

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   linux 7.3.4

Description:postgresql crashes

Details: 

I was running a test that initially insert 500 records
in a table, then it deletes 50 records, and insert 50 records every second 
by different threads, and so it maintains aprox. 450 records every point of 
time. 
The database cores with the following message printed on screen.
WARNING:  specified item offset is too large
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat  
your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat  
your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat  
your command.
Abort
Abort

I have seen this crash occurring every time, I run the test. Some time 
database crashes with in 2-6 hrs, and some time it crashes after 15 hrs. 

Please acquaint me what should I do in order to fix this problem. Write me 
an email if want more information. 

Neeraj K Sharma
Arroyo Video Solutions



---(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

[BUGS] BUG #1075: ecpg rejects C keywords in SQL context

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1075
Logged by:  Bob Showalter

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   FreeBSD 4.8

Description:ecpg rejects C keywords in SQL context

Details: 

ecpg 3.1.0
PostgreSQL 7.4.1
FreeBSD 4.8 on i386
gcc version 2.95.4 20020320 [FreeBSD]

ecpg seems to erroneously treat C keywords as errors in a SQL context. I 
discovered this after upgrading to 7.4 and compiling an existing program 
that refers to a column in one of my tables called "auto". The program 
compiles successfully on 7.3. 

Here's a simple one-line illustration of the problem:

  $ echo 'exec sql select auto from foo;' >temp.pgc
  $ ecpg temp.pgc
  temp.pgc:1: ERROR: syntax error at or near "auto"

I would think that quoting the identifier would allow it to work:

   exec sql select "auto" from foo;

but it doesn't seem to make any difference.

If I comment out the call to ScanCKeyword() at line 584 of 
src/interfaces/ecpg/preproc/pgc.l, the example above will compile 
succesfully. 



---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

[BUGS] BUG #1076: Unicode Errors using Copy command

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1076
Logged by:  mike

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Windows/Cygwin

Description:Unicode Errors using Copy command

Details: 

Hello,

I have a database I upgraded from 7.3 to 7.4.1.  When I restored the backups 
I received some error messages while the script was restoring a few 
tables(unicode errors).  The tables were created successfully but had no 
data in them.   

I dropped the database with the errors and re-created it using sql-ascii as 
the encoding, re-issued the restore command, everything was restored 
successfully. 

Next in Psql I did the following:
1)set client_environment = 'unicode';
2)Create Table unicode.Foo(
copied the sql statement to create one of the tables it failed to import 
when the default encoding was unicode but changed the table name); 
3)Insert into unicode.Foo
  Select * from sql_ascii.Foo;

The statements executed without error and the data from my sql_ascii encoded 
table was successfully copied into the new unicode table.  I did a select * 
from unicode.foo and can see the non-english punctuation in the table now. 

Thus there seems to be a problem with converting sql-ascii to unicode within 
the Copy command.  I found a few postings in pgsql-bugs questioning whether 
or not this was a problem in 7.4 but no confirmation.  No word if this is 
being worked on by anyone currently either. 

Examples of error messages I received when issuing the Copy command are the 
following: 
1)
ERROR:  invalid byte sequence for encoding "UNICODE": 0XE56C73
CONTEXT: COPY volume_reports_copy_of_public_table, line 18808, column 
transfereename: "Vralstad"(Please note I do not know how to reproduce the 
small "o" that is supposed to appear above the first letter ,a, in this 
name). 

2)
ERROR: Unicode characters greater than or equal to 0x1 are not supported
CONTEXT: COPY merged_results, line 1150, column how_make_better: " ...Konig 
was..."(again I do not know how to reproduce the two small dots that should 
appear above the letter "o" in that name/word. 

Version: Postgresql 7.4.1 on i686-pc-cygwin, compiled by GCC gcc (GCC) 3.3.1 
(cygming special). 
OS - Windows 2000 SP3.


I would like to make the default encoding for this database Unicode.  Would 
it best to do what I did above for every table in the database, drop the 
original tables, rename the new versions to the same as the original name, 
backup the database, restore the backup as a new database with the default 
Unicode encoding? 
Any other suggestions?

Mike



---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1077: install-strip does not work for MacOS X 10.2.8

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1077
Logged by:  Andrew MacRae

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   MacOS X 10.2.8

Description:install-strip does not work for MacOS X 10.2.8

Details: 


MacOS X 10.2.8, v.7.4.1 of postgreSQL, configure options: ./configure 
--with-openssl --with-perl --with-java 

The compile proceeds uneventfully and successfully.  Upon installation step 
("make install-strip"), it also generates no errors.  However, during the 
database initialization (after making the data directory, setting the 
appropriate owner, and su to the "postgres" user), the database initdb 
command generates the following error message: 


/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user 
"postgres". 
This user must also own the server process.

The database cluster will be initialized with locale C.

fixing permissions on existing directory /usr/local/pgsql/data... ok
creating directory /usr/local/pgsql/data/base... ok
creating directory /usr/local/pgsql/data/global... ok
creating directory /usr/local/pgsql/data/pg_xlog... ok
creating directory /usr/local/pgsql/data/pg_clog... ok
selecting default max_connections... 50
selecting default shared_buffers... 300
creating configuration files... ok
creating template1 database in /usr/local/pgsql/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ERROR:  could not load library 
"/usr/local/pgsql/lib/ascii_and_mic.so": dyld: /usr/local/pgsql/bin/postgres 
Undefined symbols: 
/usr/local/pgsql/lib/ascii_and_mic.so undefined reference to 
_pg_ascii2mic expected to be defined in the executable 
/usr/local/pgsql/lib/ascii_and_mic.so undefined reference to 
_pg_mic2ascii expected to be defined in the executable 


If the plain "make install" installation step is used instead (i.e. without 
any stripping), then the same initdb command succeeds with no errors, and 
everything works as expected. 

I have encountered some problems with dynamic libraries on MacOS X before 
when stripping them.  Some of the default options are okay for most binaries 
but apparently strip "too much" for a shared library, so the options have to 
be more carefully specified if one is being made.  This could be the problem 
here.  I'm sorry to be vague about this, but I do not know enough about the 
operation of dynamic/shared libraries on MacOS X to offer a more specific 
solution. 




---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

[BUGS] BUG #1078: Ref #1045 hostname lookup does not work

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1078
Logged by:  Josh Rovero

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   HP-UX 11.11

Description:Ref #1045 hostname lookup does not work

Details: 

Box configured with /etc/hosts, NIS and DNS.  Primary
source for IPs on local network is NIS, and works.
But psql (and connection attempts with libpq) fail.
Example:

uname -a
HP-UX levanto B.11.11 U 9000/800 554706577 unlimited-user license

nslookup jetstream
Using /etc/hosts on:  levanto
 
looking up FILES
Trying NIS
Name:jetstream.sonalysts.com
Address:  198.6.213.78
Aliases:  jetstream, jet

Other applications (telnet, ftp, ping) have
no problems resolving hostnames.

psql -h jetstream -U wxstat wxstation
psql: could not translate host name "jetstream" to address: host nor service 
provided, or not known 

psql -h 198.6.213.78 ... ... works.

Error does *not* occur on HP-UX B.11.00 box
with postgresql installed/built the same
way, and with identical pg_hba.conf and
postgresql.conf 


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1079: ALTER TABLE does not add foreign key

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1079
Logged by:  Vladimir Sitarchuk

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3

Operating system:   Red Hat 9

Description:ALTER TABLE does not add foreign key

Details: 

ALTER TABLE tablename ADD COLUMN columnname INT CONSTRAIN cntrname 
REFERENCES tablename2(col) 
adds the column But it does not add the foreign key constrain.



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1080: Ref #1045 resolved

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1080
Logged by:  Josh Rovero

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   HP-UX 11.11 (aka 11i)

Description:Ref #1045 resolved

Details: 

Error "psql: could not translate host name "jetstream" to address: host nor 
service provided, or not known" 

can be fixed on HP-UX 11.11 by applying HP OS patch
PHNE_27796 (libnss_dns DNS backend patch).  This patch has two patch 
dependencies which are also required: 

PHCO_29029:  libc cumulative patch
PHCO_24402: libc cumulative header patch.

Critical patch found by doing a search for getaddr in the HP patch database. 
 Unfortunately, these are *not* 
included on the update CDs are part of the recommended
patch set.


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1081: Spelling error in tsearch2.sql leading to problems with tsearch

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1081
Logged by:  Aarjav Trivedi

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux

Description:Spelling error in tsearch2.sql leading to problems with 
tsearch 

Details: 

On line 620 of tsearch2.sql which is required to install and run TSEARCH, 

REATE FUNCTION tsstat_in(cstring)

should be

CREATE FUNCTION tsstat_in(cstring)

because of this error, TSEARCH fails to work as specified,


---(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

[BUGS] BUG #1082: Order by doesn't sort correctly.

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1082
Logged by:  Richard Neill

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.4

Operating system:   Linux

Description:Order by doesn't sort correctly.

Details: 

ORDER BY sorts the following in this order:
   
Cymbal #1
Cymbal - 18 inch
Cymbal #2

It ought to be thus:

Cymbal #1
Cymbal #2
Cymbal - 18 inch

or possibly thus:

Cymbal - 18 inch
Cymbal #1
Cymbal #2


-
Here's an example sql script to reproduce the bug.


CREATE TABLE tbl_testinstruments(
instrumentidinteger,instrument 
 character varying(300)  
);

INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (1, 
'Antique Cymbals #1'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (2, 
'Antique Cymbals #2'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (3, 'Clash 
Cymbals, French - 20 inch'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (4, 
'Cymbal #1'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (5, 
'Cymbal #2'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (6, 
'Cymbal - 18 inch'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (7, 
'Cymbal, Sizzle'); 
INSERT INTO tbl_testinstruments (instrumentid, instrument) VALUES (8, 
'Cymbal, Splash'); 

SELECT instrument FROM tbl_testinstruments ORDER BY instrument;



This is the output I get:

instrument
-
 Antique Cymbals #1
 Antique Cymbals #2
 Clash Cymbals, French - 20 inch
 Cymbal #1
 Cymbal - 18 inch
 Cymbal #2
 Cymbal, Sizzle
 Cymbal, Splash
(8 rows)




-
I'm using version:

 PostgreSQL 7.3.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.1 
(Mandrake Linux 9.2 3.3.1-1mdk) 





---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1083: Insert query reordering interacts badly with NEXTVAL()/CURRVAL()

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1083
Logged by:  Martin Langhoff

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux irkutsk 2.4.25-piv-smp-server #1 SMP Fri Feb 20 
16:56:47 NZDT 2004 i686 unknown 

Description:Insert query reordering interacts badly with 
NEXTVAL()/CURRVAL() 

Details: 

=== SQL ===

CREATE TEMP TABLE testing (col_a integer, col_b integer);
CREATE TEMP SEQUENCE seq;

/* this statement will produce the expected result */
INSERT INTO testing (col_a, col_b) VALUES (NEXTVAL('seq'), CURRVAL('seq'));

/* this statement will reverse the order of CURRVAL()/NEXTVAL() to match the 
column order of the table */ 
INSERT INTO testing (col_b, col_a) VALUES (NEXTVAL('seq'), CURRVAL('seq'));

SELECT * FROM testing;

=== END SQL === 

Output looks like:

 col_a | col_b
---+---
 1 | 1
 1 | 2

I was expecting:

 col_a | col_b
---+---
 1 | 1
 2 | 2





---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1084: dropping in-use index causes "could not open relation with OID..."

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1084
Logged by:  Reece Hart

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   linux 2.4.18 (smp)

Description:dropping in-use index causes "could not open relation 
with OID..." 

Details: 

Synopsis: I have a table which I access through two pl/pgsql functions
(essentially a set/get pair). While I had several concurrent operations
through those functions, I created one index and then dropped
another.  Clients and the backend then logged "could not open relation with
OID 50491953" and all transactions stopped. 

 
  
Speculation: My suspicion is that the plan for get function used the
dropped index and that this plan wasn't invalidated when the index was
dropped.


Details:
  =>\d run_history
   Table "unison.run_history"
  Column|Type |   Modifiers
  --+-+---
   pseq_id  | integer | not null
   params_id| integer | not null
   porigin_id   | integer |
   pmodelset_id | integer |
   ran_on   | timestamp without time zone | default now()
  Indexes:
  "run_history_pq" unique, btree (params_id, pseq_id) 
   WHERE ((porigin_id IS NULL) AND (pmodelset_id IS NULL))
  "run_history_search_m" unique, btree (pseq_id, params_id, 
pmodelset_id)  
   WHERE ((porigin_id IS NULL) AND (pmodelset_id IS NOT NULL))
  "run_history_search_o" unique, btree (pseq_id, params_id, porigin_id) 
   WHERE ((porigin_id IS NOT NULL) AND (pmodelset_id IS NULL))
  "run_history_search_om" unique, btree (pseq_id, params_id, porigin_id, 
pmodelset_id) 
   WHERE ((porigin_id IS NOT NULL) AND (pmodelset_id IS NOT NULL))
  "run_history_q" btree (pseq_id)
  [snip]

The deleted index was
  "run_history_search_q" btree (pseq_id)
(I just wanted to rename it to run_history_q... serves me right for 
tinkering with index names.) 



Upon dropping the run_history_search_q index, all clients died with:
  ! Unison::Exception::DBIError occurred: ERROR:  could not open relation 
with OID 50491953 
and the backend said (once for each client):
  ERROR:  could not open relation with OID 50491953
  CONTEXT:  PL/pgSQL function "get_run_timestamp" line 8 at select into 
variables 


get_run_timestamp(integer,integer,integer,integer) is:
  => \df+ get_run_timestamp
  [snip]
  DECLARE
  q alias for $1;
  p alias for $2;
  o alias for $3;
  m alias for $4;
  z timestamp;
  BEGIN
  select into z ran_on from run_history
  where pseq_id=q
  and params_id=p
  and (case when o is null then true else porigin_id=o end)
  and (case when m is null then true else pmodelset_id=m end);
  return z;
  END; 


Indeed, OID 50491953 no longer exists in pg_class. From a backup I fished 
out: 
  -- TOC entry 809 (OID 50491953)
  -- Name: run_history_search_q; Type: INDEX; Schema: unison; Owner: unison
which shows that the missing oid is indeed the dropped index.




Thanks,
Reece



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1085: bug in the jdbc connector when doing intensive update/delete

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1085
Logged by:  Cedric

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Red Hat Linux release 8.0

Description:bug in the jdbc connector when doing intensive 
update/delete 

Details: 

We found a bug in the jdbc connector: when doing an intensive update/delete 
on a postgres 7.3.1 or 7.4.1, the generation hangs with no computer 
activity. To bypass the problem, we join 50 sql request on each database 
access. 

Our system :
* Red Hat Linux release 8.0 - Psyche
* PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2 
20020903 (Red Hat Linux 8.0 3.2-7) (same problem with 7.3.1) 
* Postgres JDBC connector jdbc2_0-stdext.jar
* Apache Tomcat/4.1.24
* Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)

What our program is doing : for a bus company, it reads all bus lines and 
calculates all possible connections to found all possible itineraries from 
any bus stop to any other bus stop. For each bus line there are different 
validities. This represents around 400 000 itineraries and around 20 000 
validities on our test platform. 

The process hang when we calculate the validities for the itineraries.

When the generation hang, the server activity and postmaster activity are 
null and the same request at the database prompt gives the exact result. The 
system is fully operationnal and the database too so we supect the jdbc 
connector. 

When we change the database version (to 7.4.1), the generation hangs quicker 
simply because Postgres is more efficient (good job, we appreciate the 30% 
performance bonus). 

By replacing many single request calls by a few request including many 
update/delete request, the process finishes well in about 1hour. 
The generation process is a thread. At first, we had about 3 
insert/update/delete requests with the same number of jdbc connections. By 
grouping update/delete request by 50, we fall to less than 700 connections. 

During hangup, there was no error messages or even warnings (tomcat logs or 
postmaster logs). 

We do not have any example to provide easily because it's a complex database 
structure. If it's really necessary, we can save all the request in a file 
and provide a dump. 

Cedric.



---(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

[BUGS] BUG #1086: lower and upper functions

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1086
Logged by:  polrus

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   cygwin on xp

Description:lower and upper functions

Details: 

lower and uper functions don't proces polish leters ąółęźżść


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] BUG #1087: psql dumps core on CTRL+ALT+\

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1087
Logged by:  Roderick van Domburg

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   FreeBSD/sparc64 5.2-CURRENT (2004-02-20)

Description:psql dumps core on CTRL+ALT+\

Details: 

Entering CTRL+ALT+\ (backslash) causes psql to dump core:

magog# psql -U pgsql template1
Password:
Welcome to psql 7.4.1, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
   \h for help with SQL commands
   \? for help on internal slash commands
   \g or terminate with semicolon to execute query
   \q to quit

template1=# Quit (core dumped)

Compiled with gcc version 3.3.3 [FreeBSD] 20031106 using "-O -ftracer 
-fprefetch-loop-arrays -fomit-frame-pointer -pipe". 


---(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

[BUGS] BUG #1088: Name resolution connecting to a database

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1088
Logged by:  Antonino Albanese

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux server.sitvallee.it 2.4.20-28.7smp #1 SMP Thu Dec 
18 11:18:31 EST 2003 i686 unknown 

Description:Name resolution connecting to a database 

Details: 

I'm using postgresql 7.4.1 exactly the rpm version:
[EMAIL PROTECTED]:~$ rpm -qva|grep -i postgresql
postgresql-docs-7.4.1-1PGDG
postgresql-devel-7.4.1-1PGDG
postgresql-contrib-7.4.1-1PGDG
postgresql-server-7.4.1-1PGDG
postgresql-libs-7.4.1-1PGDG
postgresql-7.4.1-1PGDG
postgresql-pl-7.4.1-1PGDG

on a 7.3 RH Server:
Linux server.sitvallee.it 2.4.20-28.7smp #1 SMP Thu Dec 18 11:18:31 EST 2003 
i686 unknown 

all the tests where done directly on the database
server, but I've got the same behavior from different
clients, either using psql or the php interface

trying to connect to the server with domain name
takes long time, here an example:
[EMAIL PROTECTED]:~$ time psql -h server -d newtestdb -U download -c '\q'

real0m10.151s
user0m0.010s
sys 0m0.000s

but every thing works fine if I use the IP address:
[EMAIL PROTECTED]:~$ time psql -h 192.168.0.1 -d newtestdb -U download -c '\q'

real0m0.023s
user0m0.000s
sys 0m0.020s

here the content of my configuration files:

/var/lib/pgsql/data/pg_hba.conf

local  allall ident   sameuser
hostsitvallee   download192.168.0.0 255.255.255.0   trust
hostnewtestdb   download192.168.0.0 255.255.255.0   trust
hostall all 127.0.0.1   255.255.255.255 md5
hostall all 192.168.0.0 255.255.255.0   md5


/var/lib/pgsql/data/postgresql.conf

tcpip_socket = true
max_connections = 100
shared_buffers = 64000
sort_mem = 8192
effective_cache_size = 8000
datestyle = 'sql, european'
LC_MESSAGES = 'C'
LC_MONETARY = 'C'
LC_NUMERIC = 'C'
LC_TIME = 'C'


/etc/host.conf

order hosts,bind


/etc/hosts

127.0.0.1   localhost   local   # loopback
# Local Network.
192.168.0.13capo.sitvallee.it   capo
192.168.0.14laptop.sitvallee.it laptop
192.168.0.10devwin.sitvallee.it devwin
192.168.0.12devgis.sitvallee.it devgis
192.168.0.11devweb.sitvallee.it devweb
192.168.0.230   printer.sitvallee.itprinter
192.168.0.1 server.sitvallee.it server
192.168.0.2 gateway.sitvallee.itgateway
192.168.0.5 switch.sitvallee.it switch

Hope I gave every needed information

Sincerely
Nino


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1089: pg_restore fails when restoring lo.sql functions from contrib

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1089
Logged by:  Joseph Tate

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Win32/Cygwin

Description:pg_restore fails when restoring lo.sql functions from 
contrib 

Details: 

I've been having no end to problems with pg_dump/pg_restore.  This stuff 
should just work! 

Execute the following as a user with createdb privs.
$ createdb test-lo
$ psql -f $CONTRIB/lo.sql -d test-lo
$ pg_dump --format=c --file=/tmp/test-lo.bak test-lo
$ dropdb test-lo
$ pg_restore -vCd template1 /tmp/test-lo.bak

This returns
pg_restore: connecting to database for restore
pg_restore: creating DATABASE test-lo
pg_restore: connecting to new database "test-lo" as user "postgres"
pg_restore: connecting to database "test-lo" as user "postgres"
pg_restore: creating ACL public
pg_restore: creating FUNCTION lo_in(cstring)
pg_restore: NOTICE:  type "lo" is not yet defined
DETAIL:  Creating a shell type definition.
pg_restore: creating FUNCTION lo_out(lo)
pg_restore: NOTICE:  argument type lo is only a shell
pg_restore: creating TYPE lo
pg_restore: creating FUNCTION lo_oid(lo)
pg_restore: creating FUNCTION oid(lo)
pg_restore: creating CAST CAST (public.lo AS oid)
pg_restore: creating FUNCTION lo(oid)
pg_restore: creating CAST CAST (oid AS public.lo)
pg_restore: [archiver (db)] could not execute query: ERROR:  function 
lo(oid) does not exist 
pg_restore: *** aborted because of error

To me it looks like the function is created two lines above the failure.

This works fine on Linux using 7.3.4.  It also worked on 7.2.x on Cygwin.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

[BUGS] BUG #1090: initdb does not work

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1090
Logged by:  Simon

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   windows and cygwin

Description:initdb does not work

Details: 

hi,
I installed the last version of cygwin(the version of the setup.exe is 
2.416) in my windows XP, when I want to init the postgres, it throw a error 
could you please tell me how to solve this problem

thanks in advanced
Simon

-
$ initdb -D /usr/share/postgresql/data
The files belonging to this database system will be owned by user "Simon 
Huang". 

This user must also own the server process.

The database cluster will be initialized with locale C.

creating directory /usr/share/postgresql/data... ok
creating directory /usr/share/postgresql/data/base... ok
creating directory /usr/share/postgresql/data/global... ok
creating directory /usr/share/postgresql/data/pg_xlog... ok
creating directory /usr/share/postgresql/data/pg_clog... ok
selecting default max_connections... 10
selecting default shared_buffers... 50
creating configuration files... ok
creating template1 database in /usr/share/postgresql/data/base/1... FATAL:  
coul 
d not create shared memory segment: Function not implemented
DETAIL:  Failed system call was shmget(key=1, size=1081344, 03600).

initdb: failed
initdb: removing data directory "/usr/share/postgresql/data"
 


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

[BUGS] BUG #1091: Localization in EUC_TW Can't decode Big5 0xFA40--0xFEF0.

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1091
Logged by:  yychen

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   MS-WIN2000(Run With TAIWAN Big5)

Description:Localization in EUC_TW Can't decode Big5  
0xFA40--0xFEF0. 

Details: 

In Localization:
 DataBase 
 When i save string (with Big5 0xFA40-0xFEF0) to database (encodinig with 
EUC_TW or UNICODE); and then read it. 
But PostgreSQL Can't decode these.
According to:  ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf.
3.3.4: BIG FIVE

Big Five is the encoding system used on machines that support
MS-DOS or Windows, and also for Macintosh (such as the Chinese
Language Kit or the fully-localized operating system).

  Two-byte Standard Characters  Encoding Ranges
    ^^^
  first byte range  0xA1-0xFE
  second byte ranges0x40-0x7E, 0xA1-0xFE

  One-byte Characters   Encoding Range
  ^^^   ^^
  ASCII 0x21-0x7E

The encoding used on Macintosh is quite similar to the above,
but has a slightly shortened two-byte range (second byte range up to
0xFC only) plus additional one-byte code points, namely 0x80
(backslash), 0xFD ("copyright" symbol: "c" in a circle), 0xFE
("trademark" symbol: "TM" as a superscript), and 0xFF ("ellipsis"
symbol: three dots).

 


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG #1092: Memory Fault in PQsetdbLogin

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1092
Logged by:  Fred Eisele

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Debian/GNU unstable (kernel 2.6.3)

Description:Memory Fault in PQsetdbLogin

Details: 

When opening two connections using PQsetdbLogin one of the connections was 
apparently being dropped, and I would get segmentation errors. 
I rebuilt the program using dmalloc and it reported...
debug-malloc library: dumping program, fatal error
   Error: invalid allocation size (err 40)
...when PQsetdbLogin was called.
I replaced the call to PQsetdbLogin with an equivalent call to PQconnectdb.
dmalloc does not report any errors with PQconnectdb and the original two 
problems seem to have gone away. 
As far as I am concerned, deprecating PQsetdbLogin is an adequate fix.



---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

[BUGS] BUG #1093: wrong handling of additional parameters in init script

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1093
Logged by:  Konstantin Pelepelin

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.4

Operating system:   Linux

Description:wrong handling of additional parameters in init script

Details: 

I use RPMs for linux, which contain file
/etc/rc.d/init.d/postgresql

Version for PostgreSQL 7.3.x contains some logic based on the name of script
NAME=`basename $0`
I assume, it is for support of multiple postmasters using additional files 
/etc/sysconfig/pgsql/${NAME} 

But this variable is dependable of whether this script was called by hand 
from its main location as postgresql (or using RedHat's 'service postgresql 
start') or from /etc/rc.d/rc (through symlink as S85postgresql) 


---(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

[BUGS] BUG #1094: date_part('week') bug

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1094
Logged by:  xterm

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.3.4

Operating system:   RH Fedora

Description:date_part('week') bug

Details: 

Some late dates give in some years wrong 
date_part('week')

examples:

select date_part('week', '2003-12-30'::date);
 date_part
---
 1
(1 row)

select date_part('week', '1997-12-29'::date);
 date_part
---
 1
(1 row)

but:

select date_part('week', '1998-12-31'::date);
 date_part
---
53
(1 row)




---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] BUG #1095: make can't find plperl

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1095
Logged by:  Costin

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Slackware Linux 9.1

Description:make can't find plperl

Details: 

  I am trying to configure PostgreSQL 7.4.2 with Perl 5.8.3 or 5.9.0. I 
compiled both versions of Perl, with shared libraries and with no shared 
libraries. Then I 'configure'd postgres with '--with-perl' with no error. 
  Every time I run 'make', though, I get an error that it does not find 
/pl/plperl. The problem is described by only one person I could find at url: 
http://archives.postgresql.org/pgsql-bugs/2003-09/msg00184.php.
   What do I do? please reply, I feel that I've tried everything but 
manually reprogramming perl and postgres! 


---(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

[BUGS] BUG #1096: pg_restore cannot restore large objects with other oid columns

[PostgreSQL Bugs List]

The following bug has been logged online:

Bug reference:  1096
Logged by:  Janko Richter

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux

Description:pg_restore cannot restore large objects with other oid 
columns 

Details: 

I'm using a database with tsearch2 and large objects.
When I restore the dumped  database, pg_restore tries to restore the 
functions of tsearch2 as a large object. Some  
tsearch functions are stored in tseach2 tables using the oids of the 
functions. 

It may be better, if pg_restore can skip large objects,
which do not exist. Otherwise, I can't restore the database.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org