> Well, this is sort of what AOLserver does for you without any need for
> middlemen.
i agree that AolServer is good karma,i've been reading various docs on
Aolserver since Philip Greenspun talked about it on linuxworld and i'm glad
that there's some java support being coded for it (im my opinion
I'm sure that this, if true, could certainly be the source of the problems
I've seen... I can't comment on if PHP is completely threadsafe, I know that
some of the modules (for lack of a better word) aren't, possible the ClibPDF
library I'm using. I'll check into it.
Thanks!
-Mitch
- Origin
When locale is enabled, we have always had a problem using an index
with:
col LIKE 'abc%'
We need to make this:
col LIKE 'abc%' AND
col >= "abc" AND
col < "abd"
but when locale is enabled, we can't be sure what letter is greater than
'c' in this case.
Why don'
At 10:00 PM 11/25/00 -0800, Mitch Vincent wrote:
>I've tried quite a bit to use persistent connections with PHP (for over
>a year) and always the scripts that I try to use them with behave crazy...
>The last time I tried there were problems all over the place with PHP,
>variables getting overw
At 12:07 AM 11/26/00 -0500, Alain Toussaint wrote:
>how about having a middle man between apache (or aolserver or any other
>clients...) and PosgreSQL ??
>
>that middleman could be configured to have 16 persistant connections,every
>clients would deal with the middleman instead of going direct to
> "I have all sorts of client apps, connecting in different ways, to
> my server. Some of the clients are leaving their connections open,
> but unused. How can I prevent running out of backends, and boot
> the inactive users off?"
how about having a middle man between apache (or aolserver or any
I've tried quite a bit to use persistent connections with PHP (for over
a year) and always the scripts that I try to use them with behave crazy...
The last time I tried there were problems all over the place with PHP,
variables getting overwritten, certain functions just totally breaking
(date
Franck Martin <[EMAIL PROTECTED]> writes:
> I would greatly appreciate if someone could guide me through the
> methodology to build an index for a custom type or point me to some
> readings where the algorithm is explained (web, book, etc...).
The Programmer's Guide chapter "Interfacing Extension
At 05:26 PM 11/25/00 -0700, Ron Chmara wrote:
>Note: CC'd to Hackers, as this has wandered into deeper feature issues.
>
>Tom Lane wrote:
>> GH <[EMAIL PROTECTED]> writes:
>> > Do the "persistent-connected" Postgres backends ever timeout or die?
>> No. A backend will sit patiently for the client
I looked over the last discussion of selecting IPC keys for shared memory
and semaphores (pghackers thread "shmem_seq may be a bad idea" starting
4/30/00). There were some good ideas there, but the discussion still
assumed that there would be only one postmaster running on a given port
number on
* Larry Rosenman <[EMAIL PROTECTED]> [001125 18:54]:
> > > Works. This is, umm, messy at best.
> > Err, I lied, Marc adds the /usr/local/include/tcl8.3 and tk8.3 dirs to
> > the --with-includes configure option.
> >
> > Still messy.
> and it breaks now on 7.1devel sources...
Here is what I is
* Larry Rosenman <[EMAIL PROTECTED]> [001125 18:40]:
> * Larry Rosenman <[EMAIL PROTECTED]> [001125 18:34]:
> > CONFIGURE_TCL= --with-tcl --with-tclconfig="${LOCALBASE}/lib/tcl8.3 ${LOCALBASE
>}/lib/tk8.3"
> >
> > Works. This is, umm, messy at best.
> Err, I lied, Marc adds the /usr/local/incl
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Maybe we could name the socket file .s.PGSQL.port.pid and make
> .s.PGSQL.port a symlink. Then you can find out whether the postmaster
> that created the file is still running.
Or just create a lockfile /tmp/.s.PGSQL.port#.lock, ie, same name as
soc
* Larry Rosenman <[EMAIL PROTECTED]> [001125 18:34]:
> CONFIGURE_TCL= --with-tcl --with-tclconfig="${LOCALBASE}/lib/tcl8.3 ${LOCALBASE
>}/lib/tk8.3"
>
> Works. This is, umm, messy at best.
Err, I lied, Marc adds the /usr/local/include/tcl8.3 and tk8.3 dirs to
the --with-includes configure opt
* Peter Eisentraut <[EMAIL PROTECTED]> [001125 18:26]:
> Larry Rosenman writes:
>
> > > > libpgtcl.h:19: tcl.h: No such file or directory
> > >
> > > How do you suggest going about finding the tcl.h file?
> > it's in /usr/local/include/tcl8.3/ ...
> >
> > This will be a problem with TCL as ins
Note: CC'd to Hackers, as this has wandered into deeper feature issues.
Tom Lane wrote:
> GH <[EMAIL PROTECTED]> writes:
> > Do the "persistent-connected" Postgres backends ever timeout or die?
> No. A backend will sit patiently for the client to send it another
> query or close the connection.
Larry Rosenman writes:
> > > libpgtcl.h:19: tcl.h: No such file or directory
> >
> > How do you suggest going about finding the tcl.h file?
> it's in /usr/local/include/tcl8.3/ ...
>
> This will be a problem with TCL as installed by FreeBSD PORTS...
>
> (maybe configure ought to look for it,
Tom Lane writes:
> There is a related issue on my todo list, though --- didn't we find out
> awhile back that some older Linux kernels crash and burn if one attempts
> to get an advisory lock on a socket file? (See thread 7/6/00) Were we
> going to fix that, and if so how? Or will we just tell
* Peter Eisentraut <[EMAIL PROTECTED]> [001125 17:18]:
> Larry Rosenman writes:
>
> > libpgtcl.h:19: tcl.h: No such file or directory
>
> How do you suggest going about finding the tcl.h file?
it's in /usr/local/include/tcl8.3/ ...
This will be a problem with TCL as installed by FreeBSD PORTS.
Larry Rosenman writes:
> libpgtcl.h:19: tcl.h: No such file or directory
How do you suggest going about finding the tcl.h file?
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Do local-enabled compiles have the LIKE optimization disabled always?
No. They do a run-time check to see what locale is active.
regards, tom lane
Larry Rosenman <[EMAIL PROTECTED]> writes:
> * Tom Lane <[EMAIL PROTECTED]> [001125 16:37]:
>> This story does indicate that we need a less fragile interlock against
>> starting two postmasters on one database. I have to admit that it
>> hadn't occurred to me that you could break the port-number
> I'm having a hard time believing Lamar's recollection, also. I wonder
> if there could have been some other factor involved? One possible line
> of thought: a non-locale-enabled compilation, installed to replace a
> locale-enabled one, would behave rather inconsistently if run on the
> same da
* Tom Lane <[EMAIL PROTECTED]> [001125 16:37]:
> "Joel Burton" <[EMAIL PROTECTED]> writes:
>
> This story does indicate that we need a less fragile interlock against
> starting two postmasters on one database. I have to admit that it
> hadn't occurred to me that you could break the port-number i
Trying to compile current sources using:
./configure --prefix=/home/ler/pg-test --enable-syslog \
--with-CXX --with-perl --enable-multibyte --enable-cassert \
--with-openssl --with-tcl \
--with-tclconfig=/usr/local/lib/tcl8.3 \
--with-tkconfig=/usr/local/lib/tk8.3
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Lamar Owen writes:
>> Ok, let me repeat -- the '--enable-locale' setting will not affect the
>> collation sequence problem on RedHat. If you set PostgreSQL to use
>> locale, it uses it. If you configure PostgreSQL to not use locale, the
>> collation
Lamar Owen writes:
> Ok, let me repeat -- the '--enable-locale' setting will not affect the
> collation sequence problem on RedHat. If you set PostgreSQL to use
> locale, it uses it. If you configure PostgreSQL to not use locale, the
> collation set by LANG, LC_ALL, or LC_COLLATE is _STILL_ hon
"Mitch Vincent" <[EMAIL PROTECTED]> writes:
> DEBUG: Data Base System is starting up at Sun Nov 12 18:20:04 2000
> FATAL 2: Read("/usr/local/pgsql/data/pg_control") failed: 2
> FATAL 2: Read("/usr/local/pgsql/data/pg_control") failed: 2
> Startup failed - abort
> The only compilation change I
Peter Eisentraut wrote:
> Lamar Owen writes:
> > Yes, I want to ignore their default.
> If you want to do that then the infinitely better solution is to compile
> without locale support in the first place. (Make the locale-enabled
> server a separate package.) Alternatively, the locale of the
Vince Vielhaber writes:
> $ psql -U
> psql: option requires an argument -- U
> Try -? for help.
> $ psql -?
> psql: No match.
> $
It advertises '--help' now. (And yes, '--help' works everywhere.)
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
> In xlog.c, the declaration of struct ControlFileData says:
>
> /*
> * MORE DATA FOLLOWS AT THE END OF THIS STRUCTURE - locations of data
> * dirs
> */
>
> Is this comment accurate? I don't see any sign in the code of placing
> extra data after the declared structure. If yo
Tom Lane writes:
> > I certainly don't like treating en_US specially, when in fact all locales
> > are affected by this.
>
> Well, my thought was that another locale, say en_FR, would be far more
> likely to be something that the system's user had explicitly chosen to
> use at some point,
IIRC,
Lamar Owen writes:
> Yes, I want to ignore their default.
If you want to do that then the infinitely better solution is to compile
without locale support in the first place. (Make the locale-enabled
server a separate package.) Alternatively, the locale of the postgres
user to POSIX.
> I can d
> Looks like what I would have done if I knew C.
>
> The only issue remaining is a policy issue as to if psql should call an
> editor in /tmp at all, considering the issues raised bye the recent joe
> vulnerability, ie can we trust the editor not to do a crazy thing, like
> not creating a similar
Bruce Momjian writes:
> Done. I did not change PQunixsocket or the unixsocket PQconnectdb
> connection option. Should they be changed too?
They should be removed because PQhost does this now.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
35 matches
Mail list logo
