> > First, as I've already mentioned in answer to Tom about DROP TABLE, undo
> > logic will not be implemented in 7.1 -:( Doable for tables but for
indices we
> > would need either in compensation records or in xmin/cmin in index
tuples.
> > So, we'll still live with dust from aborted xactions in o
I'm getting all of 'em, unfortunately =)
I dunno what's goin' on, but I ended up back on hackers and general, even
tho' I unsubbed from general, and was never on hackers!
Unwanted emails received : plenty
Unsolicited Postgres knowledge : pleasantly rising =)
- r
> -Original Message
Vadim Mikheev wrote:
> Hi, All
>
> First, as I've already mentioned in answer to Tom about DROP TABLE, undo
> logic
> will not be implemented in 7.1 -:( Doable for tables but for indices we
> would need
> either in compensation records or in xmin/cmin in index tuples. So, we'll
> still live
> wi
I'm getting them...
* The Hermit Hacker <[EMAIL PROTECTED]> [001029 22:36]:
>
> is anyone else getting these but me?
>
> On Sun, 29 Oct 2000, Marc G. Fournier wrote:
>
> >
> >
>
> Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
> Systems Administrator @ hub.org
is anyone else getting these but me?
On Sun, 29 Oct 2000, Marc G. Fournier wrote:
>
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
At 17:52 29/10/00 -0800, Kevin O'Gorman wrote:
>
>I'm afraid that for now, we should accept the improvements that
>have been achieved, and consider a more general treatment of
>parentheses later.
>
>What do you think?
>
Just to clarify: what is the status of the improvements that are
implemented?
most odd ...
I've taken another look at this stuff. I think it's a big improvement, but
we didn't notice that it does NOT do the thing we set out to. You
still cannot say
select foo union (((select bar)))
and as I think about it, there's no way to allow that without unifying
with c_expr. Consider: ya
* Peter Eisentraut <[EMAIL PROTECTED]> [001029 14:32]:
> Larry Rosenman writes:
>
> > Would the timezone change last night be causing this?
>
> The "timestamp" failure, yes. The "geometry", no. Geometry simply needs
> a new expected file, but unfortunately they're not the same for "cc" and
>
* Peter Eisentraut <[EMAIL PROTECTED]> [001029 14:58]:
> Larry Rosenman writes:
>
> > CC doesn't see the -O flag.
> > Why?
>
> Because C++ is not C. You can specify the flags manually with
> CXXFLAGS=...
BUT, we default C to -O, why not C++?
>
> --
> Peter Eisentraut [EMAIL PROTECTED
one list at a time, I move and test .. -hackers is the second ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
something screwed up, possibly in the configs ... subscriptions should all
be fine, but have to fix the configurations after getting these reloaded
...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED]
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
Hi, All
First, as I've already mentioned in answer to Tom about DROP TABLE, undo
logic
will not be implemented in 7.1 -:( Doable for tables but for indices we
would need
either in compensation records or in xmin/cmin in index tuples. So, we'll
still live
with dust from aborted xactions in our tab
ignore this
Would the timezone change last night be causing this?
Larry
* Larry Rosenman <[EMAIL PROTECTED]> [001029 12:55]:
> Same sources, configured as:
>
> CC=cc CXX=CC ./configure --prefix=/home/ler/pg-test --enable-syslog \
> --with-CXX --with-perl --with-includes=/usr/local/include \
>
Larry Rosenman writes:
> CC doesn't see the -O flag.
> Why?
Because C++ is not C. You can specify the flags manually with
CXXFLAGS=...
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Larry Rosenman writes:
> Would the timezone change last night be causing this?
The "timestamp" failure, yes. The "geometry", no. Geometry simply needs
a new expected file, but unfortunately they're not the same for "cc" and
"gcc"...
--
Peter Eisentraut [EMAIL PROTECTED] http://yi
Same sources, configured as:
CC=cc CXX=CC ./configure --prefix=/home/ler/pg-test --enable-syslog \
--with-CXX --with-perl --with-includes=/usr/local/include \
--with-libs=/usr/local/lib
only fails the following:
*** ./expected/timestamp.outFri Sep 22 10:33:31 2000
--- ./res
I seem to have trouble again getting cvs logs for just the 7.0.X branch.
I am running this command from a cvs checkout tree of 7.0.X:
$ cvs log -d'>2000-06-07 00:00:00 GMT' -rREL7_0_PATCHES
And am seeing entries like below. Can someone please explain why I am
seeing stuff committed in c
* Peter Eisentraut <[EMAIL PROTECTED]> [001029 10:47]:
> Larry Rosenman writes:
>
> > So, at least for the UDK FS, we probably need to walk the
> > LD_LIBRARY_PATH and cleanse it of any libraries that contain OUR libs.
>
> How do you know what your libs are? The failure is likely to occur if y
Larry Rosenman writes:
> So, at least for the UDK FS, we probably need to walk the
> LD_LIBRARY_PATH and cleanse it of any libraries that contain OUR libs.
How do you know what your libs are? The failure is likely to occur if you
you installed 7.0 in /usr/local/pgsql and followed the installat
Morning all ...
Today, we are moving the mailing lists over to the new mail
server. There *might* be a brief period where any mail sent to the lists
will be returned with a 'user unknown' error, as there will be a brief
period where the aliases will be disabled on the old server and the
When I configure PG using:
CC=cc CXX=CC ./configure --prefix=/home/ler/pg-test --enable-syslog --with-CXX
--with-perl --enable-multibyte --with-includes=/usr/local/include
--with-libs=/usr/local/lib
CC doesn't see the -O flag.
CC -g -K PIC -I/usr/local/include -I../../../src/include
-I../.
Configured as:
CC=cc CXX=CC ./configure --prefix=/home/ler/pg-test --enable-syslog --with-CXX
--with-perl --enable-multibyte --with-includes=/usr/local/include
--with-libs=/usr/local/lib
Todays sources fail regression. Here is the regression.diffs:
*** ./expected/int8.out Fri Apr 7 14:17:39
Philip Warner <[EMAIL PROTECTED]> writes:
> Just wanted to check that this was a known problem:
> ERROR: fmgr_info: language 20322 has old-style handler
> this is from current CVS when trying to call a procedure written in plpgsql.
It's certainly not a known problem --- if it were, the plpgs
Just wanted to check that this was a known problem:
ERROR: fmgr_info: language 20322 has old-style handler
this is from current CVS when trying to call a procedure written in plpgsql.
Philip Warner|
* Peter Eisentraut <[EMAIL PROTECTED]> [001029 05:48]:
> Larry Rosenman writes:
>
> > YUP, it's LD_LIBRARY_PATH.
>
> That's odd. On my system (and on all others that I've heard of that have
> it) this only affects the runtime linker, not the "ld" linker.
Maybe, but here is the tail end of ld's
I wanna know how BAR (Backup And Restore) is done now (PostgreSQL 7.0.2) and
how it will be done when PostgreSQL 7.1 comes out.
What I want is a total recover of data up to the time that the database got
scratched.
What I mean is:
Certain people write to the database all day long. Every mid-nigh
Tom,thanks for your good summary.
Seems this is the latest posting for this thread.
> -Original Message-
> From: Tom Lane
>
> Philip Warner <[EMAIL PROTECTED]> writes:
> > Do you really think it's not such a good idea to have different
> optimizer
> > behaviour for SELECT and DECLARE CUR
Larry Rosenman writes:
> YUP, it's LD_LIBRARY_PATH.
That's odd. On my system (and on all others that I've heard of that have
it) this only affects the runtime linker, not the "ld" linker.
> We need to make sure that the BUILD Unsets it...
Are you sure that this can't lead to failures if a pro
Larry Rosenman writes:
> Someone's been spending too much time on C code...
>
> the current initdb.sh uses == which doesn't work.
Works in bash. :-) Thanks.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
35 matches
Mail list logo
