Philip,
You can find the patch so far at:
http://services.csl.co.uk/postgresql/
along with a libpq thread-safe patch.
The thread referenced by Bruce's email details some of the issues
still to be looked at. The main work is integration with the build
system (testing for and linking in POSIX
I'll look into it...
On Mon, 2003-03-24 at 20:14, Christopher Kings-Lynne wrote:
set clause list (the list of SET expressions in an UPDATE statement;
section 14.12) allows a contextually typed value specification on the
right-hand side of SET assignments. One of the possibilities for a
I have been working on moving some of my software to a more SOAP
compatible interface. As I was doing it, it occured to me that a generic
function could be written, in PostgreSQL's new function manager that
allows multiple columns to be returned, that is a generic SOAP interface.
All one would
First, a SOAP query should be posted in SOAP message format, not using the
query string as you do. Second, I like the idea of calling external SOAP
services, but consider creating a language 'soap' you could do with a CREATE
FUNCTION type thing. e.g.
CREATE FUNCTION foo (TEXT) RETURNS INTEGER AS
Jason wrote:
If you can support xmlrpc instead, you'll save yourself a lot of headaches.
XML-RPC has three merits over SOAP:
1. It's a simple specification, and thus readily implemented.
2. Microsoft and IBM aren't fighting over control over it, so it's
not suffering from the we keep
On Fri, Mar 28, 2003 at 01:36:43PM -0500, [EMAIL PROTECTED] wrote:
Of course, CORBA has actually been quite formally standardized, suffers
from many fairly interoperable implementations, and is rather a lot less
bloated than any of the XML-based schemes. It might be worth trying,
too...
The
Hiroshi Inoue [EMAIL PROTECTED] writes:
How about adding a new option to skip corrupted pages ?
I have committed changes to implement checking for damaged page headers,
along the lines of last month's discussion. It includes a GUC variable
to control the response as suggested by Hiroshi.
Given
I'm curious if anyone's considered adding logic to count actual disk/cache
hits to report for EXPLAIN ANALYZE so that we get a more apples-to-apples
comparison?
The other question is whether anyone has got scripts or tools or what not
for testing and getting accurate numbers for the following
Jason M. Felice wrote:
First, a SOAP query should be posted in SOAP message format, not using the
query string as you do. Second, I like the idea of calling external SOAP
services, but consider creating a language 'soap' you could do with a CREATE
FUNCTION type thing. e.g.
CREATE
On Fri, 2003-03-28 at 14:39, mlw wrote:
I was thinking of using SOAP over HTTP as the protocol, and a
minimalist version at best. If the people want more let them add it.
I have an HTTP service class in my open source library. It would br
trivial to accept a SQL query formatted as a GET
Gary Hendricks [EMAIL PROTECTED] writes:
I'm thinking of buying Practical PostgreSQL from O'Reilly.
Has anyone got any comments on this book?
As Christopher Browne pointes out, some of the information is
outdated.
My real criticism, though, would be that *far* too much of a book
about
Hiroshi Inoue wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Hiroshi Inoue wrote:
If the cursor is INSENSITIVE, it mustn't see the row ?
Right.
If so, isn't the difference between SENSITIVE and INSENSITIVE extreme ?
Yes.
Why
A conversation with Andrew Sullivan led me to the following idea:
We have a number of frontends that like to issue BEGIN immediately
after COMMIT; so that if the client does nothing for awhile after
finishing one transaction, the backend nonetheless sees it as being
in a transaction. This
On Fri, 28 Mar 2003, Tom Lane wrote:
It seems to me that it'd be fairly easy to make BEGIN cause only
a local state change in the backend; the actual transaction need not
start until the first subsequent command is received.
[snip]
In a very real sense, the transaction snapshot defines when
I understand that internally, Postgres converts timestamps to a GMT format
and then redisplays them in the local timezone. cf:
http://groups.google.com/groups?selm=Pine.LNX.4.30.0110100104320.672-10%40peter.localdomainoe=UTF-8output=gplain
However -- doesn't this make the
On Fri, 28 Mar 2003, Tom Lane wrote:
Hiroshi Inoue [EMAIL PROTECTED] writes:
How about adding a new option to skip corrupted pages ?
I have committed changes to implement checking for damaged page headers,
along the lines of last month's discussion. It includes a GUC variable
to control
Kris Jurka [EMAIL PROTECTED] writes:
Is zeroing the pages the only / best option?
It's the only way to avoid a core dump when the system tries to process
the page. And no, I don't want to propagate the notion that this page
is broken beyond the buffer manager, so testing elsewhere isn't an
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Hiroshi Inoue wrote:
I don't understand what you two are discussing.
What's is SENSITIVE, INSENSITIVE or ASESNSITIVE ?
In SQL99 standard, I see:
- If the cursor is insensitive, then
Hiroshi Inoue wrote:
If the cursor is INSENSITIVE, it mustn't see the row ?
Right.
If so, isn't the difference between SENSITIVE and INSENSITIVE extreme ?
Yes.
Why do you or Peter refer to ASENSITIVE little ?
Not sure --- ASENSITIVE seems to be do whatever you want, which is
always
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Hiroshi Inoue wrote:
If the cursor is INSENSITIVE, it mustn't see the row ?
Right.
If so, isn't the difference between SENSITIVE and INSENSITIVE extreme ?
Yes.
Why do you or Peter refer to
Hi there,
we just released new version of tsearch V2. It's available for
testing form http://www.sai.msu.su/~megera/postgres/gist/
Changes:
* new function reset_tsearch() - reset all tsearch's caches on dictionary, parser
and config. Useful for debugging.
* It's possible to get words
Hiroshi Inoue wrote:
I don't understand what you two are discussing.
What's is SENSITIVE, INSENSITIVE or ASESNSITIVE ?
In SQL99 standard, I see:
- If the cursor is insensitive, then significant changes are not
visible.
- If the cursor is
I must have spent at least a day looking at configure threads tests
the past few months. Look at the tests in Python, OpenLDAP, MySQL,
Apache 2.0, Perl, ... each and everyone of them is different!
Ouch. Way above my experience in configure.
One of the packages (sorry cannot find my notes on which
On Friday 28 March 2003 21:30, you wrote:
Would someone take those patches and hunt around for proper 'configure'
tests? I can do the configure coding, but I don't know what tests to
make.
http://services.csl.co.uk/postgresql/
I also need configure tests for thread for one of my other
On Friday 28 March 2003 21:45, you wrote:
For testing the library, I think it is enough to init an thread attr. like
pthread_init_attr, that should be enough to test header and library.
And compiler flags, I forgot.. -pthread on freeBSD/gcc and -D_REENTRANT on
linux at least. FreeBSD needs
Yep. I need someone who knows these OS's to get some tests together.
---
Shridhar Daithankar wrote:
On Friday 28 March 2003 21:45, you wrote:
For testing the library, I think it is enough to init an thread attr. like
26 matches
Mail list logo
