On Fri, 29 Sep 2000, Bruce Momjian wrote:
The core group has decided to delay 7.1 beta until November 1. We have
done this to enable the write-ahead log code (WAL) to be shipped with
7.1.
Of course, it also gives me time to catch up on my e-mail, which I am
doing now. :-)
tell me about
On Sat, 7 Oct 2000, Alex Pilosov wrote:
Can I do following?
create table foo (
x int4 references bar*
)
Or, since 7.1 will have bar* as default for bar, will using 'references
bar' do what I want?
No, and not really. Parts of it may sort of work, but referential
actions will
On Sat, 7 Oct 2000, The Hermit Hacker wrote:
On Tue, 3 Oct 2000, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Has anybody been getting pgsql-committers messages the last few days?
Coming through fine for me (at least when hub.org isn't wedged
completely, which it was
Peter Eisentraut [EMAIL PROTECTED] writes:
I don't know if you've noticed, but the Beos porters are also reporting
that the rule test hangs. Is there any way I can help debugging this?
Yeah? Hmm, sounds more and more like a platform-specific bug then.
I don't see it on HPUX, Linux/Intel or
On Sat, 7 Oct 2000, Tom Lane wrote:
The Hermit Hacker [EMAIL PROTECTED] writes:
On Thu, 5 Oct 2000, Tom Lane wrote:
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
When is 7.1 being locked down? I may be releasing 3.1 with a few small
fixes and changes very soon.
You've probably got
Bruce Momjian [EMAIL PROTECTED] writes:
I am willing to change it to typname. Any comments?
That's hardly the only change you will have to make to get the headers
to pass through a C++ compiler without complaint. How many existing
applications do you want to risk breaking?
ParamNo probably
Well, a third party author always has the option to release his code
separately on whatever timeline seems good to him. But I think that for
third-party code included in the distribution, the same standards ought
to apply as for the Postgres code itself: we don't want people sticking
Bruce Momjian [EMAIL PROTECTED] writes:
I am willing to change it to typname. Any comments?
That's hardly the only change you will have to make to get the headers
to pass through a C++ compiler without complaint. How many existing
applications do you want to risk breaking?
ParamNo
Also, scanning through the backup file for BLOBs used in the table to be
restored will be slow, to say the least. It can be done in one pass by
building an indexed temporary table with all OID fields from the target
table, but it is definitely getting messy. Especially since Jan was talking
The file "postgres.h" (or "c.h" or "config.h", whatever is used) needs to
be the very *first* file included by each source file. Next time you
touch a source file, please check that this is the case.
The obvious failure mode is that if config.h redefines const, volatile, or
inline then it
This will be in 7.1 as WAL (write-ahead log).
On Mon, 02 Oct 2000, Hannu Krosing wrote:
"Martin A. Marques" wrote:
Hi,
I would like to know if postgres comes with some kind of backup
application? I mean something that would do database backup and restore,
something like
Plan-tree structure (output of planner): UNION/UNION ALL are handled
same as now, except that what we are appending together is not directly
the top-level plan of each leaf query, but a SubqueryScan plan scanning
the output of each leaf query. This gives us one extra level of
projection
12 matches
Mail list logo
