Re: [BUGS] Problem compiling postgresql 7.3b2

2002-10-07 Thread Peter Eisentraut
Where did the file /usr/local/lib/libbind.a come from? Who installed it and what's in it? And can you show us the config.log file? Pierre writes: > I try to compile postgresql-7.3b2 on my GNU/Linux system with gcc-3.2 > There was no problem with the configure but for the make i got this : > >

Re: [BUGS] unable to build on openbsd-sparc

2002-10-07 Thread Peter Eisentraut
Frank Van Damme writes: > To make a long story short, the build failed. I extracted the tarbal somewhere > and ran the following commands: > > # ./configure --prefix=/usr/local/postgresql-7.2.2 --enable-multibyte > --enable-odbc --with-unixodbc >configure-output 2>configure-errors You're buildin

Re: [BUGS] Passing character data to C function

2002-10-07 Thread Peter Eisentraut
Philip Compton writes: > CREATE FUNCTION pc_fn(char(50), char(50), char(255)) RETURNS Boolean > AS '/u/students/pcompton/comp442/ass4/pc_fn.so' LANGUAGE 'C'; > > //C function prototype > int pc_fn(char* a1,char* a2,char* a3){...} > or > int pc_fn(char a1[50],char a2[50],char a3[255]){...} > > fai

Re: [BUGS] postmaster will not start with stale lockfile but not report why

2002-10-07 Thread Lee Kindness
A pet annoyance with the Linux RPMs... They are shipped with syslog enabled and postmaster sdtout/stderr redirected to /dev/null. So unless the user specifically sets up the needed info in /etc/syslog.conf then they never hear a squeak from PostgreSQL! I'm by no means an RPM expert, but judging b

Re: [BUGS] Query optimizer bug

2002-10-07 Thread Stephan Szabo
On Mon, 7 Oct 2002, Szymon Juraszczyk wrote: > The table contains some 4,7 milion rows. > > Let's try to have look for entries with account = 570: > It looks to me it's estimating that 4275 rows will match account=570. If you're using 7.2 and have analyzed, you may want to up the number of

Re: [BUGS] postmaster will not start with stale lockfile but not report why

2002-10-07 Thread Tom Lane
Rudolf Potucek <[EMAIL PROTECTED]> writes: > Oct 4 14:05:45 antimony3 postgresql: Starting postgresql service: > failed > Maybe, just maybe, it would be nice if the server croaked a bit more > vebously? The postmaster croaks as verbosely as it can. I'll bet lunch that your system's startup scr

Re: [BUGS] Possible bug in PostgreSQL query planner

2002-10-07 Thread Tom Lane
Matthew Wakeling <[EMAIL PROTECTED]> writes: > I have encountered what seems to be a bad decision made by the query > planner, on a quite simple query. I have attached a shell script which > creates a large (180MB) sql script, to demonstrate the problem. These queries are forcing the join order;

[BUGS] postmaster will not start with stale lockfile but not report why

2002-10-07 Thread Rudolf Potucek
Hi! I just spent half an hour looking for the reason postgres/postmaster (on Linux Mandrake 8.2) would not start. The only thing in the log (even at debug level 4m assuming pg_ctl -o option works) was: Oct  4 14:05:43 antimony3 su(pam_unix)[3444]: session opened for user postgres b y (uid=0) Oct 

[BUGS] Query optimizer bug

2002-10-07 Thread Szymon Juraszczyk
Hi, There is a bug in Postgresql query optimizer that makes the query that's supposed to return an empty result perform considerably slower when LIMIT clause is given. For exaple, the following query: select * from login_history where account = 570 order by timestamp; is performed in 0,28 m

Re: [BUGS] Bug #789: Transaction Archival Logging -- Hot Backups

2002-10-07 Thread Jon Watte
Again, thank you for your reply. I am copying the bugs list in the hope that some ray of insight will hit. I looked at this a little more, and it seems pg_dump does not actually do what I need. If the database goes down and I lose my main data store, then I will lose all transactions back to the

[BUGS] Possible bug in PostgreSQL query planner

2002-10-07 Thread Matthew Wakeling
I have encountered what seems to be a bad decision made by the query planner, on a quite simple query. I have attached a shell script which creates a large (180MB) sql script, to demonstrate the problem. To reproduce, execute the bash script, and pipe the stdout into psql. Redirect the stdout of

Re: [BUGS] problem with composed types in plpgsql

2002-10-07 Thread Masaru Sugawara
On Mon, 7 Oct 2002 11:22:31 +0200 (CEST) Pavel Stehule <[EMAIL PROTECTED]> wrote: > I play with new beta version (7.3b2). I trayed compose types created with > create type. > > CREATE TYPE tf AS (f1 varchar(10), f2 varchar(10)); > > I wanted this type as returned type from plpgsql function. Bu

[BUGS] problem with composed types in plpgsql

2002-10-07 Thread Pavel Stehule
Hello I play with new beta version (7.3b2). I trayed compose types created with create type. CREATE TYPE tf AS (f1 varchar(10), f2 varchar(10)); I wanted this type as returned type from plpgsql function. But I didn't find how use this type in plpgsql. When I have function CREATE OR REPLACE F