From: Bryan Wu [EMAIL PROTECTED]
Subject: Urgent Question on Postgresql
Date: Sun, 18 Mar 2001 04:39:36 -0800 (PST)
Message-ID: [EMAIL PROTECTED]
Hi tatsuo Ishii,
I learn from postgresql mailing list that you are
concerning the problem the UTF8 support in Postgresql.
Currently I want to
Hi all
On Fri, 16 Mar 2001, Martin A. Marques wrote:
ld.so.1: /dbs/postgres/bin/postmaster: fatal: libz.so: open failed: No such
file or directory
Now, libz.so is in the LD_LIBRARY_PATH of the postgres user, so why is it
that Solaris doesn't load the .profile in the postgres directory.
Cyril VELTER [EMAIL PROTECTED] writes:
pg_ctl output when no shm segments left
pg_ctl: It seems another postmaster is running. Trying to start postmaster
anyway.
pg_ctl: cannot start postmaster not true !!!
Examine the log output.
DEBUG: database system was interrupted at
At a minimum, you should do a test, and if it does not yet exist, do a
sleep, then the test again.
Cyril VELTER [EMAIL PROTECTED] writes:
pg_ctl output when no shm segments left
pg_ctl: It seems another postmaster is running. Trying to start postmaster
anyway.
pg_ctl: cannot start
Tom Lane writes:
eval '$po_path' '$POSTOPTS' $logopt ''
if [ -f $PIDFILE ];then
if [ "`sed -n 1p $PIDFILE`" = "$pid" ];then
echo "$CMDNAME: cannot start postmaster" 12
echo "Examine the log output." 12
exit 1
fi
fi
which is
Bruce Momjian writes:
I see change of += in CFLAGS (harmless),
Not.
movement of #include
postgres.h, and removal of // comments, which don't appear anymore in
the code.
I only saw that the Makefile is back to how it looked at rev 1.1 before I
did some work on it. AFAICT the Makefile
Alexander Klimov writes:
There are many way to solve the problem:
the easy -- copy (or link) libz.so to /usr/lib
the clean -- avoid using LD_LIBRARY_PATH, use -R for linking instead
Our makefiles are set up to use '-R' for linking. Does this not work as
designed?
--
Peter Eisentraut
Hi friends!
I'm working in a trigger and I need to put the result
of a query into a variable.
That's very easy- apparently!
The query has a aggregate function like this:
select sum(field) into variable ...
and I'm sure that field and variable are int4 type.
So, when I run this trigger there
The Hermit Hacker wrote:
But, with shared libraries, are you really pulling in a "whole
thread-support library"? My understanding of shared libraries (altho it
may be totally off) was that instead of pulling in a whole library, you
pulled in the bits that you needed, pretty much as you
Not sure if this counts as *major*, but this jdbc1 compile
problem is presumably still there:
http://www.postgresql.org/mhonarc/pgsql-bugs/2001-03/msg3.html
as the referenced source file hasn't been updated. If I recall
right, Peter was waiting for a java 1 SDK to be installed.
On Fri, Mar 16, 2001 at 05:25:24PM -0500, Jan Wieck wrote:
Jan Wieck wrote:
...
Just to get some evidence at hand - could some owners of
different platforms compile and run the attached little C
source please?
...
Seems Tom is (unfortunately) right. The pipe blocks
Peter Eisentraut [EMAIL PROTECTED] writes:
which is clearly not giving the postmaster enough time to remove or
rewrite the pidfile. Shouldn't we put a "sleep 1" in there before
the "if"?
This is probably the best we can do.
Actually, the whole thing should only happen if we found a
* William K. Volkman [EMAIL PROTECTED] [010318 11:56] wrote:
The Hermit Hacker wrote:
But, with shared libraries, are you really pulling in a "whole
thread-support library"? My understanding of shared libraries (altho it
may be totally off) was that instead of pulling in a whole
Nat Howard writes:
Not sure if this counts as *major*, but this jdbc1 compile
problem is presumably still there:
http://www.postgresql.org/mhonarc/pgsql-bugs/2001-03/msg3.html
as the referenced source file hasn't been updated. If I recall
right, Peter was waiting for a java 1 SDK to
jreniz [EMAIL PROTECTED] writes:
So, when I run this trigger there is a mistake:
''there is no operator '=$' for types 'int4' and 'int4'
(My system is 6.5.3)
This is an old bug. Update to 7.0.3.
It might work to add spaces around the '=' signs in your trigger
function, but an update would
Alfred Perlstein [EMAIL PROTECTED] writes:
Just by making a thread call libc changes personality to use thread
safe routines (I.E. add mutex locking). Use one thread feature, get
the whole set...which may not be that bad.
Actually it can be pretty bad. Locked bus cycles needed for mutex
* Tom Lane [EMAIL PROTECTED] [010318 14:55]:
Alfred Perlstein [EMAIL PROTECTED] writes:
Just by making a thread call libc changes personality to use thread
safe routines (I.E. add mutex locking). Use one thread feature, get
the whole set...which may not be that bad.
Actually it can be
* Larry Rosenman [EMAIL PROTECTED] [010318 14:17] wrote:
* Tom Lane [EMAIL PROTECTED] [010318 14:55]:
Alfred Perlstein [EMAIL PROTECTED] writes:
Just by making a thread call libc changes personality to use thread
safe routines (I.E. add mutex locking). Use one thread feature, get
the
Peter Eisentraut [EMAIL PROTECTED] writes:
I only saw that the Makefile is back to how it looked at rev 1.1 before I
did some work on it. AFAICT the Makefile should be reverted back to the
previous revision, since the code change does not require any changes to
the Makefile.
I did this,
Larry Rosenman [EMAIL PROTECTED] writes:
I can get the code compiled, but don't have the skills to generate
a test case worthy of anything
contrib/pgbench would do as a first cut.
regards, tom lane
---(end of
I wrote:
I did this, also reinstalled the include-file changes I had made, and
then spent several fruitless hours trying to find why the "intbig" index
operators fail selftest here (on HP-PA). I suppose it's a portability
problem, since presumably they pass for Oleg ... but I don't see it.
At 19:10 14/03/01 -0500, Tom Lane wrote:
It might even make
sense for an ArchiveEntry to store both forms of the name, and then
using code could just select the form wanted instead of calling
fmtId repeatedly. Not sure.
BTW, making the -t switch compare to the unquoted name would probably
also
In 7.0.3, is it safe to drop a check constraint by simply deleting it from
the pg_relcheck table?
Chris
--
Christopher Kings-Lynne
Family Health Network (ACN 089 639 243)
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please
Doh! Not reltriggers - I meant relchecks...
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
Kings-Lynne
Sent: Monday, March 19, 2001 10:53 AM
To: Hackers
Subject: [HACKERS] Dropping CHECK constraints
In 7.0.3, is it safe to
OK, I notice I have to decrement the reltriggers field in the pg_class
directory as well, but other than that is there any problem?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
Kings-Lynne
Sent: Monday, March 19, 2001 10:53 AM
Peter,
I'll give it a try, and send the stuff to you directly, so you can
say something like "that isn't what I meant!".
Nat Howard writes:
Not sure if this counts as *major*, but this jdbc1 compile
problem is presumably still there:
"Christopher Kings-Lynne" [EMAIL PROTECTED] writes:
In 7.0.3, is it safe to drop a check constraint by simply deleting it from
the pg_relcheck table?
You'll need to adjust the relchecks count in the table's pg_class entry
as well.
regards, tom lane
Jan Wieck [EMAIL PROTECTED] writes:
Just to get some evidence at hand - could some owners of
different platforms compile and run the attached little C
source please?
(The program tests how much data can be stuffed into a pipe
or a Sys-V message queue before the
Hello All!
I have found the PostgreSQL - JDBC driver from the site
http://www.retep.org.uk/postgres/.
But, Iam not finding any tutorial for the same.
Can anybody tell me the name of the site where I can find both the
PostgreSQL driver and tutorial containing the examples .
With regards,
Sourabh
I just returned from vacation and identified the problem.
We'll fix it.
Regards,
Oleg
On Sun, 18 Mar 2001, Tom Lane wrote:
I wrote:
I did this, also reinstalled the include-file changes I had made, and
then spent several fruitless hours trying to find why the
Since pg_upgrade will not work for 7.1, should its installation be
prevented and the man page be disabled?
Probably. I am not sure it will ever be used again now that we have
numeric file names.
Perhaps we should leave it for 7.1 because people will complain when
they can not find
Thomas Lockhart [EMAIL PROTECTED] writes:
If it doesn't work, and will not be made to work, then let's remove it
from the tree.
I tend to agree with Peter's slightly less drastic proposal: remove it
from the installed fileset and disable its man page, without necessarily
'cvs remove'ing all
32 matches
Mail list logo
