Hi,
Every time i explain what is the fsync parameter for, the next thing i
always say is: "never turn it off", and now that we have
synchronous_commit there is no good reason for turn fsync off... so
why are we still let it be in the postgresql.conf where it's so
vulnerable to a misguided dba?
ev
On Thu, Dec 31, 2009 at 7:45 PM, Kevin Grittner
wrote:
> Robert Haas wrote:
>
>> What predicate locking? If you take ACCESS EXCLUSIVE locks on every
>> read, that should serialize all access to every table. Predicate
>> locking wouldn't do anything, because the table would be completely
>> inacce
Robert Haas wrote:
> What predicate locking? If you take ACCESS EXCLUSIVE locks on every
> read, that should serialize all access to every table. Predicate
> locking wouldn't do anything, because the table would be completely
> inaccessible to all competing transactions.
Yeah, that's the benef
On Thu, Dec 31, 2009 at 4:44 PM, Kevin Grittner
wrote:
>> I wonder if you couldn't start with something ridiculously poor,
>> like maybe an S2PL implementation with only table-level granularity
>> - just make any operation that reads or writes a table grab an
>> ACCESS EXCLUSIVE lock until transac
On Thu, Dec 31, 2009 at 5:37 PM, Tom Lane wrote:
> Robert Haas writes:
>> Anyhow, that brings me back to the question I asked upthread, which is
>> "Can/should we suck one of these libraries into our code base (and if
>> so, which?) or do we need to add an analogue of --with-libxml so that
>> we
Greg Stark wrote:
> aaah... I think I see where we've gone off track in previous
> discussions...you think postgres keeps row level locks in a shared
> memory data structure. It doesn't it stores all row level locks
> *in* the tuple itself. It only stores the lock in memory briefly
> while actua
On Dec 31, 2009, at 3:41 PM, Tom Lane wrote:
>> My question is: why is the group membership of the foo_bar, foo_baz,
>> and foo_yow roles not reflected in pg_group?
>
> Per the fine manual:
>
> The view pg_group exists for backwards compatibility: it emulates a
> catalog that existed in PostgreS
"David E. Wheeler" writes:
> My question is: why is the group membership of the foo_bar, foo_baz,
> and foo_yow roles not reflected in pg_group?
Per the fine manual:
The view pg_group exists for backwards compatibility: it emulates a
catalog that existed in PostgreSQL before version 8.1. It show
Tatsuo Ishii writes:
> Done. Inclded are C test program along with modified fe-exec.c.
> The modification made to fe-exec.c is sending Sync after Parse, Bind
> and Describe. Pgpool-II does this in order to get current transaction
> status.
I tried this but didn't have any luck crashing the backe
Fellow Hackers,
Given this SQL:
BEGIN;
CREATE ROLE foo WITH NOLOGIN;
CREATE ROLE foo_bar WITH LOGIN PASSWORD '***' INHERIT IN ROLE foo;
CREATE ROLE foo_baz WITH LOGIN PASSWORD '***' INHERIT IN ROLE foo;
CREATE ROLE foo_yow WITH LOGIN PASSWORD '***' INHERIT
IN ROLE
aaah... I think I see where we've gone off track in previous
discussions...you think postgres keeps row level locks in a shared
memory data structure. It doesn't it stores all row level locks *in*
the tuple itself. It only stores the lock in memory briefly while
actually acquiring the lock. Once
Robert Haas writes:
> Anyhow, that brings me back to the question I asked upthread, which is
> "Can/should we suck one of these libraries into our code base (and if
> so, which?) or do we need to add an analogue of --with-libxml so that
> we can link against an external library if present and omit
Robert Haas wrote:
Anyhow, that brings me back to the question I asked upthread, which is
"Can/should we suck one of these libraries into our code base (and if
so, which?) or do we need to add an analogue of --with-libxml so that
we can link against an external library if present and omit the
f
Jeff Davis wrote:
> I started a wiki page here:
>
> http://wiki.postgresql.org/wiki/Serializable
I'll try to get that filled in with something useful over the
weekend. I'm heading to a party soon, and may not be in shape to
work on it tomorrow ;-)
Happy New Year, all!
-Kevin
--
S
I wrote:
> It's just a little bit of a stretch to call SILOCKs locks, because
> they don't actually block anything. They are used at various points
> to see where a transaction is reading data which has been modified
> by another transaction or vice versa. And they do need to be kept
> until all
Robert Haas wrote:
> OK. I think it will become more clear whether the existing lock
> data structures are adequate as you move into detailed design.
I've gotten far enough in reviewing it to be pretty convinced that
they'll cover all the granularities I'm likely to want unless I get
to the po
On Thu, 2009-12-31 at 15:18 -0500, Tom Lane wrote:
> Simon Riggs writes:
> > Why not get both max() and min(), then rebase the histogram according to
> > those values. That way the histogram can still move significantly and
> > the technique will still work.
>
> Define "rebase", keeping in mind t
On Thu, Dec 31, 2009 at 11:12 AM, Andrew Dunstan wrote:
> David E. Wheeler wrote:
>> On Dec 31, 2009, at 1:04 AM, Peter Eisentraut wrote:
>>>
>>> I think the primary use will be to load a JSON value into Perl or Python
>>> and process it there. So a json type that doesn't have any interesting
>>>
On Thu, 2009-12-31 at 09:11 -0600, Kevin Grittner wrote:
> Yeah, that's why this is a two to four year project.
I started a wiki page here:
http://wiki.postgresql.org/wiki/Serializable
I didn't add much content yet, but can participants in this discussion
please try to organize the various issu
2009/11/23 Teodor Sigaev :
> Hi there,
>
> attached is a patch, which contains implementation of a red-black
> tree, a self-balanced implementation of binary tree. The main goal of
> this patch is to improve creation time of GIN index in the corner cases.
> While creation, GIN collects data in m
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> I agree that you have a problem to solve, but defining the problem as
> "please can we have SET ROLE back" is not going to lead you to a secure
> solution.
Fair enough. Thanks for the analysis.
--Ian
--
Sent via pgsql-
"Turner, Ian" writes:
>> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>> Really? What can it contain, and how are you enforcing that?
> Anything except a function call. We look for non-keyword identifier
> followed by open parenthesis, which is probably excessively
> restrictive.
I'm afraid this
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Really? What can it contain, and how are you enforcing that?
Anything except a function call. We look for non-keyword identifier followed by
open parenthesis, which is probably excessively restrictive. I'd rather have
s
"Turner, Ian" writes:
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>> Exactly. If that's what you want, we can talk about it, but *SET ROLE
>> doesn't solve that problem*. In fact, a security definer function is a
>> lot closer to solving that problem than SET ROLE is. The premise of SET
>> ROL
Simon Riggs writes:
> Why not get both max() and min(), then rebase the histogram according to
> those values. That way the histogram can still move significantly and
> the technique will still work.
Define "rebase", keeping in mind that this has to work on datatypes that
we don't have a distance
On Thu, Dec 31, 2009 at 1:43 PM, Kevin Grittner
wrote:
> Robert Haas wrote:
>> It seems to me that the hard part of this problem is to describe
>> the general mechanism by which conflicts will be detected, with
>> specific references to the types of data structures that will be
>> used to hold th
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Exactly. If that's what you want, we can talk about it, but *SET ROLE
> doesn't solve that problem*. In fact, a security definer function is a
> lot closer to solving that problem than SET ROLE is. The premise of SET
> R
Heikki Linnakangas writes:
> Turner, Ian wrote:
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>>> Actually, I don't find that to be a given. Exactly what use-cases have
>>> you got that aren't solved as well or better by calling a SECURITY DEFINER
>>> function owned by the target role?
>>
>> Oh,
Turner, Ian wrote:
>> -Original Message-
>> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>> Actually, I don't find that to be a given. Exactly what use-cases have
>> you got that aren't solved as well or better by calling a SECURITY DEFINER
>> function owned by the target role?
>
> Oh, that
On Wed, 2009-12-30 at 14:55 -0500, Tom Lane wrote:
> Actually, in the problematic cases, it's interesting to consider the
> following strategy: when scalarineqsel notices that it's being asked for
> a range estimate that's outside the current histogram bounds, first try
> to obtain the actual curr
Tom Lane writes:
> Actually, in the problematic cases, it's interesting to consider the
> following strategy: when scalarineqsel notices that it's being asked for
> a range estimate that's outside the current histogram bounds, first try
> to obtain the actual current max() or min() of the column v
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> BTW, it looks like the patch is showing a manual change to
> >> pg_config.h.in. Don't do that. Run autoheader.
>
> > I wasn't aware autoheader existed. Is that new or has it alwasy been
> > part of autoconf?
>
> It's always been
Robert Haas wrote:
> It seems to me that the hard part of this problem is to describe
> the general mechanism by which conflicts will be detected, with
> specific references to the types of data structures that will be
> used to hold that information.
Well, the general approach to tracking SIR
On Wed, Dec 30, 2009 at 7:41 PM, David E. Wheeler wrote:
> On Dec 30, 2009, at 4:17 PM, Robert Haas wrote:
>
>>> That much works currently. Behind the scenes, when a stored procedure is
>>> loaded into plperl the code ref for the perl sub is stored in a cache.
>>> Effectively just
>>> $cache{$n
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Actually, I don't find that to be a given. Exactly what use-cases have
> you got that aren't solved as well or better by calling a SECURITY DEFINER
> function owned by the target role?
Oh, that's easy: If you want to do t
Bruce Momjian writes:
> Tom Lane wrote:
>> BTW, it looks like the patch is showing a manual change to
>> pg_config.h.in. Don't do that. Run autoheader.
> I wasn't aware autoheader existed. Is that new or has it alwasy been
> part of autoconf?
It's always been there, or at least for many years
On Thu, Dec 31, 2009 at 12:10 PM, Kevin Grittner
wrote:
> Greg Stark wrote:
>
>> Hm, this raises the issue that you'll have to figure out what
>> should happen if two different transactions are using different
>> isolation modes. Currently our two isolation modes only control
>> behaviour within
On Dec 30, 2009, at 2:54 PM, Tim Bunce wrote:
> That handles the arity of the calls and invokes the right SP, bypassing
> SQL if the SP is already loaded.
Nice.
> That much works currently. Behind the scenes, when a stored procedure is
> loaded into plperl the code ref for the perl sub is stored
Tom Lane wrote:
> Magnus Hagander writes:
> > Attached patch is the part of the win64 patch that changes Datum to be
> > uintptr_t, and associated changes, with only very minor changes from
> > me. It also includes autoconf tests that I tricked Bruce into fixing
> > for me :-)
>
> > Comments?
>
On Thu, 2009-12-31 at 13:14 +0100, Andres Freund wrote:
> > > When cancelling a backend that behaviour could be a bit
> annoying ;-)
> >
> > Reading comments alone doesn't show the full situation here.
> >
> > Before we send signal we check pid also, so the chances of this
> > happening are fairl
2009/12/31 Tom Lane :
> Magnus Hagander writes:
>> 2009/12/31 Tom Lane :
>>> Where's the logic to provide a definition of
>>> intptr_t if the platform fails to?
>
>> autoconf does that.
>
> Oh, that's what I get for trying to review a patch before absorbing
> any caffeine :-( ... I missed that yo
On Thu, Dec 31, 2009 at 10:36 PM, Tom Lane wrote:
> Gurjeet Singh writes:
> > We are seeking to enable SET ROLE in security-definer functions,
> since @
> > D.E Shaw there are scripts from the past that used this feature, and I
> think
> > you'd also agree that SET ROLE is security definer f
Magnus Hagander writes:
> 2009/12/31 Tom Lane :
>> Where's the logic to provide a definition of
>> intptr_t if the platform fails to?
> autoconf does that.
Oh, that's what I get for trying to review a patch before absorbing
any caffeine :-( ... I missed that you were relying on a built-in
autoc
Greg Stark wrote:
> Hm, this raises the issue that you'll have to figure out what
> should happen if two different transactions are using different
> isolation modes. Currently our two isolation modes only control
> behaviour within your transaction so they co-exist perfectly fine.
>
> ISTM you
Gurjeet Singh writes:
> We are seeking to enable SET ROLE in security-definer functions, since @
> D.E Shaw there are scripts from the past that used this feature, and I think
> you'd also agree that SET ROLE is security definer functions has it's uses.
Actually, I don't find that to be a giv
2009/12/30 Teodor Sigaev :
> Sync with current CVS
I have reviewed this patch and it looks good to me. The only
substantive question I have is why gist_point_consistent() uses a
different coding pattern for the box case than it does for the polygon
and circle cases? It's not obvious to me on the
2009/12/31 Tom Lane :
> Magnus Hagander writes:
>> Attached patch is the part of the win64 patch that changes Datum to be
>> uintptr_t, and associated changes, with only very minor changes from
>> me. It also includes autoconf tests that I tricked Bruce into fixing
>> for me :-)
>
>> Comments?
>
>
Magnus Hagander writes:
> Attached patch is the part of the win64 patch that changes Datum to be
> uintptr_t, and associated changes, with only very minor changes from
> me. It also includes autoconf tests that I tricked Bruce into fixing
> for me :-)
> Comments?
This is a joke no? Where's the
Peter Eisentraut writes:
> The definition of c.h is bogus anyway. You might think it contains
> includes and defines to set up a portable C environment, which is what
> the first half indeed does.
> But then things like regproc, transaction ID types, IntArray, varlena,
> bytea, oidvector, NameDa
On Thu, Dec 31, 2009 at 3:11 PM, Kevin Grittner
wrote:
> Yeah, that's why this is a two to four year project. And I would
> point out that if there *wasn't* a performance hit in serializable
> mode, none of the other isolation levels would exist. These less
> rigorous modes exist precisely becau
David E. Wheeler wrote:
On Dec 31, 2009, at 1:04 AM, Peter Eisentraut wrote:
I think the primary use will be to load a JSON value into Perl or Python
and process it there. So a json type that doesn't have any interesting
operators doesn't sound useless to me. The features I would like to
Sorry,guys, my mistakes, the keywords list should be sorted , and I
just append xmlquery at the end of keyword list , that is why parser does
not call makexmlexpr.Instead, the parser try to find a function to match
xmlquery and faild.
2009/12/31 fangfang liu
> thanks for Xquery info, I do not st
Attached patch is the part of the win64 patch that changes Datum to be
uintptr_t, and associated changes, with only very minor changes from
me. It also includes autoconf tests that I tricked Bruce into fixing
for me :-)
Comments?
Unless there are objections, I'll go ahead and apply this one for
b
On Dec 31, 2009, at 1:04 AM, Peter Eisentraut wrote:
> I think the primary use will be to load a JSON value into Perl or Python
> and process it there. So a json type that doesn't have any interesting
> operators doesn't sound useless to me. The features I would like to get
> out of it are input
On Thu, 2009-12-31 at 15:41 +0100, Joachim Wieland wrote:
> I still think that we should have three transaction cancel modes, one
> to cancel an idle transaction, another one to cancel a running query
> and a third one that just cancels the transaction regardless of it
> being idle or not. This la
Greg Stark wrote:
> The unsolved problems that have been raised are:
> [legion]
Yeah, that's why this is a two to four year project. And I would
point out that if there *wasn't* a performance hit in serializable
mode, none of the other isolation levels would exist. These less
rigorous modes
thanks for Xquery info, I do not start to implenment the xmlquery() itself ,
maybe call xqilla lib or sth else in the future.
I think xmltable is almost equal to xmlquery , except that it retuns
talbeset insead of xml.
I take xmlconcat as an example , add xmlquery whereever xmlconcat appers and
no
yes,whereever xmlconcat appears.
2009/12/31 Alvaro Herrera
> fangfang liu escribió:
>
> > IS_XMLQUERY is added in primenodes.h
> >
> > but the parser can not find xmlquery, the makeXmlExpr is not called at
> all.
>
> Did you add it to keywords.c etc?
>
> --
> Alvaro Herrera
> http://www.CommandP
On Thu, Dec 31, 2009 at 3:03 PM, Simon Riggs wrote:
> This patch extends SIGINT to allow cancellation of transactions while
> idle in both HS and normal mode. It also changes the standard message
> reported on an idle transaction in aborted state to ' in
> transaction (aborted)', so that once abor
"Albe Laurenz" wrote:
> But with "snapshot isolation" (what our "serializable" corresponds
> to) you cannot see rows updated after snapshot creation, right?
>
> So phantom reads cannot occur, but we still are not truly
> serializable.
My previous reply missed your point entirely, didn't it?
L
fangfang liu escribió:
> IS_XMLQUERY is added in primenodes.h
>
> but the parser can not find xmlquery, the makeXmlExpr is not called at all.
Did you add it to keywords.c etc?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Cus
fangfang liu wrote:
you mean create and replace funtion xmlquery()?
maybe you are right, but I still want to know why parser does not find
xmlquery.
We would have to see your code to know why it didn't do what you expect.
What exactly are you intending that this function would do anywa
On Thu, Dec 31, 2009 at 12:45 PM, Nicolas Barbier
wrote:
> * To answer your specific question: T0 might not read that specific
> row, but the COUNT(..) definitely must read *something* that must be
> modified by T1 when it updates the ishighlander field:
The problem occurs when the update happens
"Albe Laurenz" wrote:
> See the example I concocted in
> http://archives.postgresql.org/pgsql-hackers/2009-05/msg00316.php
Sure, let's look at that example. Of course, *any* transaction run
by itself won't show differences from true serializable behavior
*regardless* of the mode in which it ru
On Thu, 2009-12-31 at 11:10 +, Simon Riggs wrote:
> On Thu, 2009-12-24 at 21:38 +0100, Joachim Wieland wrote:
> > On Sun, Dec 6, 2009 at 4:23 PM, Tom Lane wrote:
> > > We are using NOTICE, not NOTIFY, assuming that we use anything at all
> > > (which I still regard as unnecessary). Please sto
Hi All,
We are seeking to enable SET ROLE in security-definer functions, since
D.E Shaw has a usage for this, and I think you'd also agree that SET ROLE is
security definer functions has it's uses.
As the code stands right now, I see that the only concern against
enabling SET ROLE in SecD
On ons, 2009-12-30 at 11:46 +0900, Hitoshi Harada wrote:
> 2009/12/30 Tom Lane :
> > Hitoshi Harada writes:
> >> I found the struct IntArray defined in c.h is actually used only in
> >> execQual.c. ISTM the definition should be at least moved to the right
> >> place.
> >
> > It's a general-purpose
Hi All,
We are seeking to enable SET ROLE in security-definer functions, since @
D.E Shaw there are scripts from the past that used this feature, and I think
you'd also agree that SET ROLE is security definer functions has it's uses.
As the code stands right now, I see that the only conce
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Doesn't seem insurmountable, though, just one more thing to think
> about as we're having this conversation. Someone else will need to
> weigh in on this point though, as I don't use JSON in a way that would
> make anything beyond validation
2009/12/31 Sergej Galkin :
> typedef struct moving_object
> {
> double x_high;
> double y_high;
> double x_low;
> double y_low;
> time_t mov_time;
> double x_plus;
> double y_plus;
> double x_minus;
> double y_minus;
> } moving_object;
[..]
> #define DatumGetM
[ Reviving this old thread because a recent one referred to it. ]
2009/5/7 Albe Laurenz :
> Kevin Grittner wrote:
>
>> > maybe I misunderstood something.
>> >
>> > Consider a function
>> > "makehighlander(personid integer) RETURNS void"
>> > defined like this:
>> >
>> > SELECT ishighlander INT
On Wed, Dec 30, 2009 at 4:56 PM, Robert Haas wrote:
>
> From my point of view, what makes a patch invasive is the likelihood
> that it might break something other than itself. For example, your
> patch touches the core planner code and the core GIST code, so it
> seems possible that adding suppor
2009/12/31 Bruce Momjian :
> I must be missing something but I thought the only problem with our
> existing snapshot system was that you could see a row updated after your
> snapshot was created, and that the solution to that was to abort the
> transaction that would see the new row. Can you tell
On Thursday 31 December 2009 12:25:19 Simon Riggs wrote:
> On Wed, 2009-12-30 at 20:06 +0100, Andres Freund wrote:
> > Hm. I just read a bit of that multiplexing facility (out of a different
> > reason) and I have some doubt about it being used unmodified for
> > canceling backends:
> >
> > procsig
Hello all,
I'm creating gist index for testing purpuses :)
I created index element structure:
typedef struct moving_object
{
double x_high;
double y_high;
double x_low;
double y_low;
time_t mov_time;
double x_plus;
double y_plus;
double x_minus;
double y_minus;
you mean create and replace funtion xmlquery()?
maybe you are right, but I still want to know why parser does not find
xmlquery.
thanks.
2009/12/31 Peter Eisentraut
> On tor, 2009-12-31 at 19:22 +0800, fangfang liu wrote:
> > Actually, I expect the function looks like xmlquery(xmlcontent,xquery
On tor, 2009-12-31 at 19:22 +0800, fangfang liu wrote:
> Actually, I expect the function looks like xmlquery(xmlcontent,xquery)
> and return the query result.
You don't need to modify the parser for that at all. You can implement
that in user-space as a user-defined function.
--
Sent via pgs
On Wed, 2009-12-30 at 20:06 +0100, Andres Freund wrote:
> Hm. I just read a bit of that multiplexing facility (out of a different
> reason)
> and I have some doubt about it being used unmodified for canceling backends:
>
> procsignal.c:
> /*
> * Note: Since there's no locking, it's possible th
Actually, I expect the function looks like xmlquery(xmlcontent,xquery) and
return the query result.
So xmlconcat(xml1,xml2) become a good example to study.
starting from gram.y, I try to make parser to call xmlquery,the following is
the result of diff:
diff gram.y c:\new_gram.y
449c449
< XM
On Thu, 2009-12-24 at 21:38 +0100, Joachim Wieland wrote:
> On Sun, Dec 6, 2009 at 4:23 PM, Tom Lane wrote:
> > We are using NOTICE, not NOTIFY, assuming that we use anything at all
> > (which I still regard as unnecessary). Please stop injecting confusion
> > into the discussion.
>
> Attached i
2009/12/31 Magnus Hagander :
> 2009/12/4 Tsutomu Yamada :
> A bit further down, it has:
>
> + /* The size of `void *', as computed by sizeof. */
> + #define SIZEOF_VOID_P 4
> +
>
>
> shouldn't that be 8 for win64 platforms?
Nevermind this second comment. Now that it's no longer 1AM, I see that
thi
are only numeric and temporal
ones but we don't have such limitation.
- add "+"/"-" operator search code in parsing, which is used to
calculate frame bound, but I'm not sure if this is right approach.
- add more regression tests
Regards,
--
Hitoshi Harada
more_f
On ons, 2009-12-30 at 12:55 -0500, Greg Smith wrote:
> Basically, configure failed on their OpenBSD system because thread
> safety is on but the libxml2 wasn't compiled with threaded support:
> http://xmlsoft.org/threads.html
>
> Disabling either feature (no --with-libxml or --disable-thread-sa
On ons, 2009-12-30 at 13:23 -0500, Andrew Dunstan wrote:
> I'd like to see at
> least the outline of an API before we go any further. JSON is, shall
> we
> say, lightly specified, and doesn't appear to have any equivalent to
> XPath and friends, for example. How will we extract values from a
> J
On ons, 2009-12-30 at 12:53 -0500, Robert Haas wrote:
> It looks like they are all very permissive, though I wonder what the
> legal effect of a license clause that the software be used for Good
> and not Evil might be.
It's not without issues, apparently:
http://grep.be/blog/en/computer/legal/go
On Thu, Dec 31, 2009 at 3:33 AM, fangfang liu wrote:
> Hi - Does anyone know how to add a xml support function into postgresql?
>
> I want to add a function named xmlquery into postgresql.
>
> I modify gram.y by adding xmlquery relatedcode wherever other xml support
> functions appear.
> but the p
Hi - Does anyone know how to add a xml support function into postgresql?
I want to add a function named xmlquery into postgresql.
I modify gram.y by adding xmlquery relatedcode wherever other xml support
functions appear.
but the parser can not find xmlquery, the makeXmlExpr is not called at all.
Bruce Momjian wrote:
> I must be missing something but I thought the only problem with our
> existing snapshot system was that you could see a row updated after your
> snapshot was created, and that the solution to that was to abort the
> transaction that would see the new row. Can you tell me wha
88 matches
Mail list logo