OK, I have a pretty good guess about the cause of the ODBC shutdown
failure message in the server logs. Sending 'X' is still causing the
error message.
The error you are seeing is from the backend libpq code, the area that
communicates with clients.
So, let's assume the problem is not the platf
> If I had known that this was possible I would have done it myself already.
> ;-) This is a good idea in general because in a default installation
> pgaccess won't find libpgtcl on any system because it doesn't have the
> benefit of the -rpath/-R business. Please review/remove the note at the
t;
> ===
> Patrick Dunford, Christchurch, NZ - http://pdunford.godzone.net.nz/
>
>In this way, love is made complete among us so that we will have
> confidence on the day of judgment, bec
I checked the logs, and we released the new 6.4 backend protocol on
1998-10-30. That was 2.5 years ago.
We normally allow older clients to communicate with newer servers, but
often we don't support newer clients talking to older servers, sometimes
even servers one release in the past. The reaso
will have
confidence on the day of judgment, because in this world we are
like him.
-- 1 John 4:17
http://www.heartlight.org/cgi-shl/todaysverse.cgi?day=20010210
===
Created by Mail2Sig - http://pdunford.godzone.net.nz/software/mail2sig/
OK, I have ifdef'ed out the sending of the 'X' parameter. I will see if
placing it somewhere else will help. Could it have to do with the fact
we are in a transaction in ODBC? My guess is that the X is returning
data that is triggering the error.
[ Charset ISO-8859-1 unsupported, converting...
> At 12:23 10/02/01 -0500, Bruce Momjian wrote:
> >I am inclinded to remove this open item:
> >
> > New SQL function setval(seq,val,bool) for use in pg_dump (Philip)
> >
> >The use of the 3rd parameter, 'iscalled', while used by pg_dump, is not
> >of general use, so we probably don't need to d
At 12:23 10/02/01 -0500, Bruce Momjian wrote:
>I am inclinded to remove this open item:
>
> New SQL function setval(seq,val,bool) for use in pg_dump (Philip)
>
>The use of the 3rd parameter, 'iscalled', while used by pg_dump, is not
>of general use, so we probably don't need to document it.
Here is info about distributed lock manager by IBM:
http://oss.software.ibm.com/developerworks/opensource/linux/projects/dlm/
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830
> Bruce Momjian writes:
>
> > I have applied the following patch for OpenBSD and FreeBSD. They have
> > the same -Bsymbolic handling and same use of LD for linking. I made the
> > duplicate changes Peter made for BSDI.
>
> Hmm, at least on OpenBSD the recommended way to build shared libraries
Bruce Momjian writes:
> I have applied the following patch for OpenBSD and FreeBSD. They have
> the same -Bsymbolic handling and same use of LD for linking. I made the
> duplicate changes Peter made for BSDI.
Hmm, at least on OpenBSD the recommended way to build shared libraries is
using 'ld'
> > -Bsymbolic requires all symbols in the library to be resolvable at link
> > time. If you use 'ld' then you will need to provide all the appropriate
> > files yourself. The compiler driver normally does that automatically.
> >
>
> Great. I see you modified Makefile.bsdi to properly know it
I am inclinded to remove this open item:
New SQL function setval(seq,val,bool) for use in pg_dump (Philip)
The use of the 3rd parameter, 'iscalled', while used by pg_dump, is not
of general use, so we probably don't need to document it. Is this valid?
Info on the new param is:
---
> So, how to resolve that conflict? I think it's better for the script
> default to cater to the manual-invocation case, because you're more
> likely to forget to add the switch when you're entering the command by
> hand. When pg_ctl is invoked from a system shutdown script, you only
> have to g
> You can't hardcode "gcc" like that. I've committed some fixes that should
> work for you. Please try them out. Also try to build libpq++.
>
> > It seems the -Bsymbolic needs the gcc, while other links are OK with ld.
> > We may find this is true on many platforms.
>
> -Bsymbolic requires al
Bruce Momjian writes:
> I replaced the 'ld' with 'gcc -Wl', and that prevents the need for the
> crt1.o.
>
> It still requires -lc:
>
> ifneq ($(PORTNAME), bsdi)
> LINK.shared += $(shlib_symbolic)
> else
> LINK.shared = gcc -shared -Wl,-Bsymbolic,-soname,$(soname)
>
"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
>> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
>> Just curious. I
>> just think that waiting by default and smart shutdown don't really mix
>> well.
> Current behavior prevents manual shutdown from cancelling
> running sessions carelessly.
Seem
> Bruce Momjian writes:
>
> >> Allow location of Unix domain socket to be configurable (David J. MacKenzie)
> >> Allow postmaster to listen on a specific IP address (David J. MacKenzie)
> >> Allow socket path name to be specified in hostname by using leading slash
> >> (David J. MacKenzie)
> >> A
> Bruce Momjian writes:
>
> > I just tried gcc and got:
> >
> > #$ gcc -shared -soname libpsqlodbc.so.0 -Bsymbolic info.o bind.o
> > columninfo.o connection.o convert.o drvconn.o environ.o execute.o lobj.o
> > misc.o options.o pgtypes.o psqlodbc.o qresult.o results.o socket.o
> > parse.o statemen
> > Just curious. I
> > just think that waiting by default and smart shutdown don't really mix
> > well.
> >
>
> Current behavior prevents manual shutdown from cancelling
> running sessions carelessly.
> OTOH it's the dba's responsibilty to write appropriate shutdown
> scripts and it's not goo
Tim,
I've found your message in postgres hackers list and wondering if
sourceforge db part could be improved using our recent (7.1) GiST improvements.
In short, using RD-Tree + GiST we've added index support for arrays of
integers. For example, in our rather busy web site we have pool
of online
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
>
> Hiroshi Inoue writes:
>
> > > Since there were no comments, I'm going to make fast shutdown
> the default.
> > >
> >
> > Oh I've misunderstood.
> > I object to the change.
>
> Do you feel the current behaviour
Bruce Momjian writes:
> I just tried gcc and got:
>
> #$ gcc -shared -soname libpsqlodbc.so.0 -Bsymbolic info.o bind.o
> columninfo.o connection.o convert.o drvconn.o environ.o execute.o lobj.o
> misc.o options.o pgtypes.o psqlodbc.o qresult.o results.o socket.o
> parse.o statement.o gpps.o tuple
OK, I have added this conversion scripts to CVS along with Thomas's. If
someone wants to merge them into one, feel free to submit a patch. I
have provided a URL to my2pg.pl to retrieve the most recent version.
The only license issue was that the bottom of the source code had a
mention referring
> Bruce Momjian writes:
>
> > > The -Bsymbolic switch is the same on all platforms that have it. You can
> > > link without it, but then you won't actually be able to use the ODBC
> > > driver. It seems like you need to link in a few other libraries to
> > > resolve all symbols.
> >
> > OK, if
I have removed the following open item by adding the other mysql
conversion utility to the CVS tree in /contrib/mysql:
Merge MySQL/PgSQL translation scripts
If someone wants to merge them and make one script out of them, go
ahead. Both are BSD licensed now.
The only remaining source co
Bruce Momjian writes:
> > The -Bsymbolic switch is the same on all platforms that have it. You can
> > link without it, but then you won't actually be able to use the ODBC
> > driver. It seems like you need to link in a few other libraries to
> > resolve all symbols.
>
> OK, if this is true on
> > > Bruce Momjian writes:
> > >
> > > > I have applied the following patch to properly exit ODBC. I also
> > > > patched the ODBC makefile so it links under BSD/OS. The -Bsymbolic
> > > > under BSD/OS is very harsh under BSD/OS, requiring all symbols even in
> > > > libc and crt1.o to be reso
> > Bruce Momjian writes:
> >
> > > I have applied the following patch to properly exit ODBC. I also
> > > patched the ODBC makefile so it links under BSD/OS. The -Bsymbolic
> > > under BSD/OS is very harsh under BSD/OS, requiring all symbols even in
> > > libc and crt1.o to be resolved before
> Bruce Momjian writes:
>
> > I have applied the following patch to properly exit ODBC. I also
> > patched the ODBC makefile so it links under BSD/OS. The -Bsymbolic
> > under BSD/OS is very harsh under BSD/OS, requiring all symbols even in
> > libc and crt1.o to be resolved before creating the
Bruce Momjian writes:
> I have applied the following patch to properly exit ODBC. I also
> patched the ODBC makefile so it links under BSD/OS. The -Bsymbolic
> under BSD/OS is very harsh under BSD/OS, requiring all symbols even in
> libc and crt1.o to be resolved before creating the shared libr
Hiroshi Inoue writes:
> > Since there were no comments, I'm going to make fast shutdown the default.
> >
>
> Oh I've misunderstood.
> I object to the change.
Do you feel the current behaviour is more intuitive? Just curious. I
just think that waiting by default and smart shutdown don't really
32 matches
Mail list logo
