Marc G. Fournier [EMAIL PROTECTED] writes
I've done a grep through the code, to see if its something that we do use,
and
it doesn't seem to come back with anything ... I believe its considered
common knowledge that 'swapping' for a database is evil, so am wondering
if there is some way that
Merlin Moncure [EMAIL PROTECTED] writes:
Doing some testing on upcoming 8.1 devel and am having serious
issues
with new bitmap index scan feature. It is easy to work around (just
disable it) but IMO the planner is using it when a regular index
scan
should be strongly favored.
I think
Dear PostreSQL hackers,
For the interested, here:
http://www.cs.utwente.nl/~hiemstra/courses/reports/sqlxml.pdf
you find a little report discussing possibilities to implement the
SQL/XML standard using the PostgreSQL extension mechanism. The report is
written by Master students following the
Hi Michael,
i want to support explicit commit/rollback support
in pl/pgsql instead of using autocommit feature.
my requirement is to know how transactions work in
postgres generally and how to support transaction
managment in pl/pgsql
thanks for your help.
--
Asif Ali.
--- Michael Fuhr
Ali Baba wrote:
Hi Michael,
i want to support explicit commit/rollback support
in pl/pgsql instead of using autocommit feature.
The fine manual is your friend:
http://www.postgresql.org/docs/8.0/static/transaction-iso.html
Djoerd,
http://www.cs.utwente.nl/~hiemstra/courses/reports/sqlxml.pdf
you find a little report discussing possibilities to implement the
SQL/XML standard using the PostgreSQL extension mechanism. The report is
written by Master students following the course XML Databases at U
Twente.
Paul, Rob,
I just read with some interest your paper on XML queries with PostgreSQL.
I'm particularly puzzled by some of your conclusions, and thought you might
want to discuss them with the PGSQL-Hackers mailing list.
Particulary:
Functions should be able to have a variable amount of
I'm thinking about GiST approach http://www.cs.arizona.edu/xiss/
Oleg
On Thu, 18 Aug 2005, Djoerd Hiemstra wrote:
Dear PostreSQL hackers,
For the interested, here:
http://www.cs.utwente.nl/~hiemstra/courses/reports/sqlxml.pdf
you find a little report discussing possibilities to implement the
IIRC, Peter Eisentraut noted a while ago that implementing the SQL/XML
functions properly would require building them into the postgresql
parser as special cases. That of course would mean we wouldn't be using
the extension mechanism, and is something we should normally shy away
from, but I
Folks,
Those of you who went to OSCON may have heard that SpikeSource is having a
contest to increase testing code coverage of popular OSS projects. The
contest involves prizes of up to $2500 for test writers.
Given that we have people in the community who have been thinking about
testing,
Hi there,
I don't understand why this select doesn't works:
regression=# select coalesce(
tp_rewrite_substitute(ARRAY[query, test.target, test.sample]),
query)
from test,to_tsquery('new2 york2 hotel') as query
where query @
Oleg,
ERROR: column query.query must appear in the GROUP BY clause or be
used in an aggregate function
Apparently the parser thinks you have an aggregate function in there. Do
you?
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of
I believe I've traced down the cause of the Assert trap in VACUUM FULL
that Teodor reported here:
http://archives.postgresql.org/pgsql-hackers/2005-06/msg01278.php
The case that VACUUM is tripping up on is one in which some concurrent
transaction (call it X1) updates and then later deletes a row.
I have just managed to get pg server and client (cvs tip) talking IPv6
on Windows. :-)
1. Building
- added in library in configure.in:
AC_CHECK_LIB(ws2_32, main)
- faked out getaddrinfo test in resulting configure and force answer
to yes
- added these lines to
On Thu, Aug 18, 2005 at 03:48:55PM -0400, Tom Lane wrote:
The only solution I can see (short of abandoning lazy VACUUM) is that
we have to make the code that follows t_ctid chains more wary. That
code is already aware (at least in the places I looked at) that a t_ctid
link might lead to an
Andrew Dunstan [EMAIL PROTECTED] writes:
. what do we do about the getaddrinfo test? I'm almost inclined not to
do it on windows, and assume that if we have ws2_32.dll we have it.
There's something mighty fishy about that. AC_REPLACE_FUNCS works on
Windows for the other cases it's used for
(Prompted by nearby thread about VACUUM FULL bugs, but not having
anything to do with that properly speaking.)
Hackers,
For some time, I have wondered: what does postgres use t_ctid chains
for? It seems like it is useful to find the newer version of a
tuple. However, wouldn't that
Alvaro Herrera [EMAIL PROTECTED] writes:
Interesting failure mode. While reading it I was suddenly struck by the
thought that overwriting storage managers may somehow be more resistent
to these kind of failures. This may well be true, because there is
never need for a VACUUM process which
The definition in WS2tcpip.h
WINSOCK_API_LINKAGE
int
WSAAPI
getaddrinfo(
IN const char FAR * nodename,
IN const char FAR * servname,
IN const struct addrinfo FAR * hints,
OUT struct addrinfo FAR * FAR * res
);
(IN, FAR, and OUT are #defined to empty string).
Paul Tillotson [EMAIL PROTECTED] writes:
For some time, I have wondered: what does postgres use t_ctid chains
for? It seems like it is useful to find the newer version of a
tuple. However, wouldn't that eventually get found anyway? A
sequential scan scans the whole table, and so it will
IPv6 exists in a production quality state only in XP sp1, XP sp2, and
Windows 2003.
There was an optional prototype stack for 2000, but not production
quality and not installed by default. XP non-service-pack had IPv6,
but not production-quality.
One thing you could do is dynamically load
The mingw header has pretty much this with WINSOCK_API_LINKAGE IN OUT
and FAR dissolved away.
The standard test complains about it being an unresolved reference when
it is declared as char getaddrinfo (); . If we remove that and instead
include the header the test passes. I have no idea
I think it's because it's __stdcall, and the name gets mangled to
include the number of parameters.
-Original Message-
From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 18, 2005 4:44 PM
To: Chuck McDevitt
Cc: Tom Lane; PostgreSQL-development
Subject: Re:
Chuck McDevitt wrote:
I think it's because it's __stdcall, and the name gets mangled to
include the number of parameters.
Aha! now it makes sense. How do we get around that in the configure tests?
cheers
andrew
---(end of
Dear Josh and Andrew,
Thanks for the prompt replies. For now it's just a paper. It was Rob and
Pim's mission to find out if the SQL /XML standard can be implemented
using the postgresql extension mechanism. Building it into the parser was
no option.
Best, Djoerd.
On Thu, 18 Aug 2005, Andrew
Andrew Dunstan [EMAIL PROTECTED] writes:
Chuck McDevitt wrote:
I think it's because it's __stdcall, and the name gets mangled to
include the number of parameters.
Aha! now it makes sense. How do we get around that in the configure tests?
I thought it might be something like that ... but the
On Wed, 17 Aug 2005, Stephan Szabo wrote:
On Tue, 16 Aug 2005, Stephan Szabo wrote:
On Tue, 16 Aug 2005, Tom Lane wrote:
I think this would take some generalization of afterTriggerInvokeEvents,
which now might or might not find the target rel in the EState it's
passed, but
27 matches
Mail list logo
