Can you provide a link or
> info that doesn't require login please?
The relevant content of the ticket is basically just:
Description: WebSphere Application Server support for JDBC access to
PosgreSQL databases.
Use case: In WAS, be able to define and use JDBC providers and
datasources p
with commercial vendors. I'd
love to tell my customers that we can support this natively with
Postgres!
And by the way THANK YOU for the amazing tsearch, it's a beautiful
piece of software and very useful to us.
Thanks,
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Sour
> > SQL = ''SELECT * INTO temp1 FROM '' || $1;
>
> I tried this, and it seems that "SELECT ... INTO foo" is not executed
> correctly by EXECUTE --- the INTO is handled as an ordinary select-into-
> table construct rather than plpgsql's select-into-variable.
>
> While I have not looked closel
> > > su - postgres sh -c "$DAEMON stop >& /dev/null"
> >
> > Hmm... What is wrong here, besides the '>&'? The '>&' can be
> > replaced with '2>&1 >' if that is more standard.
It won't do what you want. You want '>/dev/null 2>&1'.
> Change made.
Hmmm, I don't see this change in cvsweb.
F
> It would probably be better if the socket files weren't in /tmp but in
> a postgres-owned directory. However, at this point we have a huge
> backwards compatibility problem to overcome if we want to move the
> socket files. The location of the socket files is essentially a core
> part of the f
/tmp is for *temporary* files. Such a lock is not a temporary file, it
should go somewhere in /var, why not in /var/lib/pgsql/data ?
> The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> file after the server has run 6 days. This will be a problem.
>
> We could touch (o
