Savepoints will be implemented after WAL.
Vadim
> I was wondering, is it a possibility/projected to have nested
> transactions in postgres? Would MVCC support that?
>
> What I would like is following:
> begin tran a;
> do some work;
> begin tran b;
> do some other work
> rollback b;
Hi,
I was wondering, is it a possibility/projected to have nested transactions
in postgres? Would MVCC support that?
What I would like is following:
begin tran a;
do some work;
begin tran b;
do some other work
rollback b;
...
commit a;
Alternatively, is there a way to trap an except
* Tom Lane <[EMAIL PROTECTED]> [001008 18:57] wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I should have also said that since this is pretty reproducable I'd
> > be happy to run with patches for stronger assertion checks
>
> If you're not running with --enable-cassert configured, I'
> > If anyone has suggestions/additions to this list it would be greatly
> > appreciated!
>
> I'm very interested in helping with this (it is on my list of projects
> and I've managed to stop adding new ones to the list for now). Should
> we take this off-list, or keep it here?
Michael Fork <[EMAIL PROTECTED]> writes:
> When I execute the following two queries, the results differ -- with the
> only change being that another table is joined (a 1-1 join that should not
> affect the results -- I reduced down a much larger query that was
> exhibiting the behavior to what app
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> The patches ad, ae, and af will cause configure to fail on machines
>> without mktemp. It's not like things get "screwed up" for me, but the
>> point of Autoconf is portability to *all* machines, so FreeBSD-specific
>> changes/optimizations(?) seem mis
> Bruce Momjian wrote:
> >
> > Can someone comment on this?
>
> You can tell we're getting close to beta when Bruce combs through the
> archives :-)
Man, we have been around here too long. :-)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I should have also said that since this is pretty reproducable I'd
> be happy to run with patches for stronger assertion checks
If you're not running with --enable-cassert configured, I'd certainly
recommend trying that.
reg
> The Hermit Hacker writes:
>
> > Okay, autoconf on hub.org is based on what is in ports ... the only
> > "custom patches" are that which are in /usr/ports/devel/autoconf/patches,
> > and I just went through them and there doesn't look like anything *odd* in
> > there ... can you look at those pa
When I execute the following two queries, the results differ -- with the
only change being that another table is joined (a 1-1 join that should not
affect the results -- I reduced down a much larger query that was
exhibiting the behavior to what appears to be the cause). I know that
views have so
The Hermit Hacker writes:
> Okay, autoconf on hub.org is based on what is in ports ... the only
> "custom patches" are that which are in /usr/ports/devel/autoconf/patches,
> and I just went through them and there doesn't look like anything *odd* in
> there ... can you look at those patches and te
"Vladimir V. Zolotych" wrote:
> Hello all,
>
> Compile with
> $ g++ -I/usr/local/qt/include -o days.so -shared days.cpp
IIRC you have to compile as days.o and then link to .so:
g++ -o days.o
ld -shared -o days.so days.o
I don't know if the compiler gets it right in one line. It might.
C
* Alfred Perlstein <[EMAIL PROTECTED]> [001008 03:52] wrote:
>
> Unfortunatly I'm still getting crashes, this one looks like it's
> during a vacuum, previously I got a crash while doing an UPDATE, but
> in exactly the same spot, it took quite a bit longer to provoke this
> time:
I should have al
> > > > PostgreSQL would probably "play" better with other products if
> > > > the DEBUG macro had a prefix, maybe PGSQLDEBUG or similar.
> > > >
> > > > Until there is some fix in this area, plperl will not build with
> > > > a version of perl that has debugging enabled.
> > > >
>
> It even got
The referential integrity doesn't work properly with inheritance I
think. It would be nice if it was fixed to work with inheritance but
that would probably also need inheritable indexes to work (?? I don't
know how much ref integrity relies on having an index in place).
Alex Pilosov wrote:
>
>
In the up and coming version of postgres there will be a special column
called "tableoid" which gives the oid from pg_class of the table it came
from. If you are not using the current CVS sources, you will have to
keep a column updated yourself.
Alex Pilosov wrote:
>
> Suppose I have table a and
* Alfred Perlstein <[EMAIL PROTECTED]> [001006 16:02] wrote:
> * Tom Lane <[EMAIL PROTECTED]> [001004 09:56] wrote:
> > Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > > I have a reliable way to make postgresql crash after a
> > > couple of hours over here and a backtrace that looks like a good
>
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > IMHO we should make -S be configurable in postgresql.conf and let
> > users choose what they want.
>
> I agree. Mind you, I think we should discourage use of -S, because it
> makes troubleshooting so much more difficult. But we shouldn't remove
> t
18 matches
Mail list logo
