2010/1/8 Kevin Grittner kevin.gritt...@wicourts.gov:
Nicolas Barbier nicolas.barb...@gmail.com wrote:
I assume here that PG's non-SI-compatible behavior of not always
rollbacking any transaction that writes to a non-last version will
be disabled in serializable mode.
Can that currently
2010/1/8 Markus Wanner mar...@bluegap.ch:
SIREAD atop predicate locking serves detecting vulnerable edges (I hope
I'm using that term correctly here) between newly inserted tuples and
reads, right? I was trying to figure if it would make sense to use
predicate locking (instead of table or row
2010/1/7 Markus Wanner mar...@bluegap.ch:
(It's interesting that with database page level granularity, he states
that predicate locking would not be necessary. Instead any page can be
locked at any time. For this to work, according to my reasoning, you'd
have to know in advance on which page
2010/1/7 Albe Laurenz laurenz.a...@wien.gv.at:
I don't know if such a thing would be easy to implement in
PostgreSQL, but I had thought that the standard approach to
implement predicate locking is like this:
Whenever you touch (read) a data structure, you tag it with a lock
that prevents
2010/1/7 Albe Laurenz laurenz.a...@wien.gv.at:
Nicolas Barbier wrote:
In such a pure implementation of predicate locking, the overlap
testing is be done using the algebraic properties of the conditions,
which is of course extremely difficult (if not impossible) to
implement perfectly
2009/12/31 Bruce Momjian br...@momjian.us:
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.
[ Reviving this old thread because a recent one referred to it. ]
2009/5/7 Albe Laurenz laurenz.a...@wien.gv.at:
Kevin Grittner wrote:
maybe I misunderstood something.
Consider a function
makehighlander(personid integer) RETURNS void
defined like this:
SELECT ishighlander INTO
2009/12/31 Sergej Galkin sergej.gal...@gmail.com:
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;
[..]
2009/12/18 Florian Weimer fwei...@bfk.de:
* Florian Pflug:
On 16.12.09 16:40 , Kevin Grittner wrote:
Nicolas Barbiernicolas.barb...@gmail.com wrote:
I am not sure whether the serialization failures that it may cause
are dependent on the plan used.
They are.
But so are failures due
[ Forgot the list, resending. ]
2009/12/16 Boszormenyi Zoltan z...@cybertec.at:
Robert Haas írta:
On Wed, Dec 16, 2009 at 1:25 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Dec 16, 2009 at 1:14 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
So you'd have to disable HOT
2009/12/16 Albe Laurenz laurenz.a...@wien.gv.at:
Quote:
The problem [of phantom reads] was identified in (Eswaran et al., 1976),
but the general purpose predicate locking solution suggested there
has not been widely adopted because of the difficulty in testing mutual
satisfiability
2009/12/15 Tom Lane t...@sss.pgh.pa.us:
to...@tuxteam.de writes:
(and as Andrew Dunstan pointed out off-list: I was wrong with my bold
assertion that one can squeeze infinitely many (arbitrary length)
strings between two given. This is not always the case).
Really? If the string length is
2009/9/15 Michael Meskes mes...@postgresql.org:
Looking at
http://zlew.org/postgresql_static_check/scan-build-2009-09-14-1/report-3LPmKK.html#EndPath
it tells me that the value stored to 'counter' is never used. However, the
counter++ is called inside a loop and thus will be read the next
2009/8/23 Magnus Hagander mag...@hagander.net:
For another data point, Microsoft documentation says:
This POSIX function is deprecated beginning in Visual C++ 2005. Use
the ISO C++ conformant _hypot instead.
_hypot() has been there since Windows 95, so it shouldn't be a problem
to use it -
2009/6/7 Markus Wanner mar...@bluegap.ch:
However, there's no special whitespace treatment. Nor anything remotely
as clever as nearby variable renaming. There's no such magic, the
developer still needs to tell the tool what he wants.
If I understand correctly, nearby variable renaming refers
, then we
don't need this feature at the moment. Otherwise: Could anyone
explain?
That is exactly what it means.
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
dictionary
* specifies maximum length - add the before maximum
14.12. Example of Creating a Parser
* Note it should - insert that after Note
* The void function - replace The with This
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
---(end
There are (of course) competing standards such as:
url:http://en.wikipedia.org/wiki/High_Level_Shader_Language
and:
url:http://en.wikipedia.org/wiki/Cg_%28programming_language%29.
greetings,
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
recursively (implementation doesn't have to
be recursive, of course), to eliminate whole sub-trees of the join
tree.
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
---(end of broadcast)---
TIP 9: In versions below 8.0
that looks suspiciously similar to a
DBMS optimizer.
Maybe it is debatable whether this optimization should be done by the
application (i.e. the ORM) or by the DBMS. I am personally in favor of
doing it in the DBMS.
greetings,
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word
attributes are used in the query.
Hibernate:
url:http://www.hibernate.org/
Hibernate Inheritance Mapping:
url:http://www.hibernate.org/hib_docs/reference/en/html/inheritance.html
greetings,
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
of these
passes has to be fully executed, because one needs to read at least
all the data once to find the top n.
greetings,
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
---(end of broadcast)---
TIP 5: don't
of the outer query:
SELECT * FROM (
SELECT
ROW_NUMBER() OVER (ORDER BY key ASC) AS rownumber,
columns
FROM tablename
) AS foo
WHERE rownumber = 10
(example stolen from the Wikipedia article linked above).
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
, in which update-in-place is
safe. (No transaction can guarantee that it will commit.)
Updates to row values that did not escape the currect transaction
yet (ie, rows that were created by or have their last value written by
the current transaction).
Nicolas
--
Nicolas Barbier
http://www.gnu.org
%20Optimizer/index.html
The manual:
url:http://www.postgresql.org/docs/current/static/planner-optimizer.html
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On 11/20/05, Heikki Linnakangas [EMAIL PROTECTED] wrote:
On Sat, 19 Nov 2005, Nicolas Barbier wrote:
You might want to take a look at the pages that I set up to track the
progress on my master's thesis:
url:http://www.nicolas.barbier.easynet.be/itsme/thesis/
especially
to
find all these papers with Google (Scholar) in case my computer is
shut down, otherwise you can download them directly from me.
Greetings,
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
---(end of broadcast
101 - 127 of 127 matches
Mail list logo
