Hello,everyone, I want to know how postgres remain its unique index unique after i have change it,Forexample: CREATE TABLE human(age INT,name CHAR(30));then in pg_attribute catalog the unique index pg_attribute_relid_attnum_index will use the relid of'human' and attnum of age to create a index tupl
Alvaro Herrera <[EMAIL PROTECTED]> writes:
>>> In current (as of a couple hours ago) clean CVS tip sources, without any
>>> of my local changes, I'm getting a postmaster segfault when trying to
>>> connect to a non existant database.
Alvaro, did you figure this out? I've been mostly distracted fo
Marc G. Fournier wrote:
> On Fri, 30 Apr 2004, Bruce Momjian wrote:
>
> > But we don't want to have all our developers controlled by one feature
> > being completed. It isn't fair. They should get a good warning about
> > freeze starting.
>
> Nor is it fair to extend the development cycle indef
On Fri, 30 Apr 2004, Bruce Momjian wrote:
> But we don't want to have all our developers controlled by one feature
> being completed. It isn't fair. They should get a good warning about
> freeze starting.
Nor is it fair to extend the development cycle indefinitely waiting for
that one feature i
On Fri, 30 Apr 2004, Matthew T. O'Connor wrote:
> And if we always set deadlines independent of the required development
> time, then we may never get a win32 port or any other major feature that
> takes a little more time and attention.
Actually, that one doesn't hold ... it just means that we n
Marc G. Fournier wrote:
> On Fri, 30 Apr 2004, Bruce Momjian wrote:
>
> > Marc G. Fournier wrote:
> > > On Thu, 29 Apr 2004, Tom Lane wrote:
> > >
> > > > I guess my point is really "do you want to freeze on June 1 if *none* of
> > > > these features are done?"
> > >
> > > No, I agree that that wo
On Fri, 30 Apr 2004, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Thu, 29 Apr 2004, Tom Lane wrote:
> >
> > > I guess my point is really "do you want to freeze on June 1 if *none* of
> > > these features are done?"
> >
> > No, I agree that that would be foolish ... but there has also been
Marc G. Fournier wrote:
On Thu, 29 Apr 2004, Matthew T. O'Connor wrote:
I know it's a chicken and egg problem, do we set a date for developers
to shoot for, or do shoot for specific features and choose a date from
there. I think there can no hard and fast rule on this, it depends on
the feature
Claudio Natoli <[EMAIL PROTECTED]> writes:
> That's my 2c. I don't see anything that can't make a June 1 deadline
> (assuming we are expected to keep to it! :-)... the only unknown for me is
> the sync/fsync code Tom is doing, only as I have no idea where he is up to.
> I've been AWOL for a month,
Marc G. Fournier wrote:
> On Thu, 29 Apr 2004, Tom Lane wrote:
>
> > I guess my point is really "do you want to freeze on June 1 if *none* of
> > these features are done?"
>
> No, I agree that that would be foolish ... but there has also been alot
> done on the code over the past few months that
On Thu, 29 Apr 2004, Tom Lane wrote:
> I guess my point is really "do you want to freeze on June 1 if *none* of
> these features are done?"
No, I agree that that would be foolish ... but there has also been alot
done on the code over the past few months that even *one* of those
features should be
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > On Thu, 29 Apr 2004, Tom Lane wrote:
> >> In the first place it's unfair to other developers to make schedule
> >> slips at the last moment, and especially to *plan* to do so.
>
> > Isn't it equally unfair to slip the scheduale t
Claudio Natoli wrote:
>
>
> > > Win32 has continued on a steady pace for six months now.
> >
> > Be honest ... 6 months ago, did you believe the Win32 work would have
> > taken >6 months? How many of the current issues could you have
> > anticipated? How many will crop up in the next month?
>
> > Win32 has continued on a steady pace for six months now.
>
> Be honest ... 6 months ago, did you believe the Win32 work would have
> taken >6 months? How many of the current issues could you have
> anticipated? How many will crop up in the next month?
FWIW, the backend porting effort sta
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Thu, 29 Apr 2004, Tom Lane wrote:
>> In the first place it's unfair to other developers to make schedule
>> slips at the last moment, and especially to *plan* to do so.
> Isn't it equally unfair to slip the scheduale that developers that have
> b
Marc G. Fournier wrote:
> On Thu, 29 Apr 2004, Bruce Momjian wrote:
>
> > Marc is concerned that folks will not work hard to meet a deadline and
> > will slack off if we push thing to July 1.
>
> I don't think I'm so muc worried about that as under-estimating the amount
> of time required to fini
> The other point, especially about Win32, is to see if we can
> spread the load a bit. Perhaps Claudio, Magnus, Merlin and Bruce
> should start trying to farm out specific tasks.
Here are the tasks, off the Win32 page, I see as necessary to drop in:
* Handle sync() by opening all file ope
Simon Riggs wrote:
> > Agreed we want to allow the superuser control over writing of the
> > archive logs. The question is how do they get access to that. Is it by
> > running a client program continuously or calling an interface script
> > from the backend?
> >
> > My point was that having the
On Thu, 29 Apr 2004, Bruce Momjian wrote:
> Marc is concerned that folks will not work hard to meet a deadline and
> will slack off if we push thing to July 1.
I don't think I'm so muc worried about that as under-estimating the amount
of time required to finish them ... its not like *that's* neve
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > *If* June 1st comes along, and Win32 isn't ready, there is nothing wrong
> > with freezing the code *except* for a pending Win32 patch ...
>
> Yeah there is ...
>
> In the first place it's unfair to other developers to make sche
Marc G. Fournier wrote:
Personally, I think there are alot of large features that ppl have been
hard at getting complete in time for June 1st that we should stick to it,
else we're going to end up with 'yet another release' delayed in hopes
that the outstanding bugs in Win32 will get fixed in a re
On Thu, 29 Apr 2004, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > *If* June 1st comes along, and Win32 isn't ready, there is nothing wrong
> > with freezing the code *except* for a pending Win32 patch ...
>
> Yeah there is ...
>
> In the first place it's unfair to other dev
=?gb2312?B?emh1YW5namlmZW5n?= <[EMAIL PROTECTED]> writes:
> PGh0bWw+PHByZT48UFJFPmhlbGxvLDxCUj5ldmVyeW9uZSE8QlI+Jm5ic3A7
> SSB3YW50IHRvIGtub3cgaG93IHBvc3RncmVzcWwgcmVtYWluIGl0cyB1bmlx
> dWUgaW5kZXggdW5pcXVlIGFmdGVyIDxCUj5pIGhhdmUgY2hhbmdlIGl0LkZv
> ciBleGFtcGxlOjxCUj4mbmJzcDtjcmVhdGUgdGFibGUgaHVtYW
> Simon Riggs wrote:
> > Is there a definitive list of supported ports? (for anything)
>
> http://www.postgresql.org/docs/7.4/static/supported-platforms.html
>
> For example the Linux/arm port can run on many PDA's but because of the
> write intensity and the limited write cycles of flash memory th
Simon Riggs wrote:
> Is there a definitive list of supported ports? (for anything)
http://www.postgresql.org/docs/7.4/static/supported-platforms.html
For example the Linux/arm port can run on many PDA's but because of the
write intensity and the limited write cycles of flash memory this
continu
Simon Riggs <[EMAIL PROTECTED]> writes:
> ... I'm looking into PostgreSQL on small
> handheld devices. Clearly these have limited memory and little "disk"
> capability...
> Are there some ports available to various devices?
I don't know of any supported ports.
> What is the lowest memory footpri
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> *If* June 1st comes along, and Win32 isn't ready, there is nothing wrong
> with freezing the code *except* for a pending Win32 patch ...
Yeah there is ...
In the first place it's unfair to other developers to make schedule
slips at the last moment,
Seemingly completely opposite to my usual focus on large scale
enterprise issues and requirements, I'm looking into PostgreSQL on small
handheld devices. Clearly these have limited memory and little "disk"
capability...
Are there some ports available to various devices?
What is the lowest memory
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Thu, 29 Apr 2004, Merlin Moncure wrote:
>> So I suggest (my choices are of course subjective):
>> Dividing
>> win32 'should fix' (installer, /contrib, etc.)
>> win32 'must fix' (psql query cancel, <1970 dates, non-cygwin regression)
> actually, I
On Thu, 2004-04-29 at 20:50, Marc G. Fournier wrote:
> On Thu, 29 Apr 2004, Bruce Momjian wrote:
>
> > Merlin Moncure wrote:
> > > Bruce Momjian wrote:
> > > > Yes, it was vague. The question is now that we are a month away, do
> > > we
> > > > want to target June 1, mid-June, or July 1.
> > >
>
On Thu, 29 Apr 2004, Simon Riggs wrote:
> What I would add is: if PITR and Win32 do make it into the release, I
> would strongly urge for an extended beta period. It would not prove good
> press if 100,000 new Windows users tripped over on various issues, nor
> even 1 press-worthy user was unable
On Thu, 2004-04-29 at 20:24, Bruce Momjian wrote:
> I am willing to work on this...
There is much work still to be done to make PITR work..accepting all of
the many comments made.
If anybody wants this by 1 June, I think we'd better look sharp. My aim
has been to knock one of the URGENT items on
On Thu, 2004-04-29 at 20:24, Bruce Momjian wrote:
> Simon Riggs wrote:
> >
> > The archiver should be able to do a whole range of things. Basically,
> > that point was discussed and the agreed approach was to provide an API
> > that would allow anybody and everybody to write whatever they wanted.
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 29, 2004 12:45 PM
> To: Bruce Momjian
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Call for 7.5 feature completion
>
>
> Bruce Momjian wrote:
> > Well, if Win32 doesn't complete by June 1, d
On Thu, 29 Apr 2004, Merlin Moncure wrote:
> Bruce Momjian wrote:
> > Well, if Win32 doesn't complete by June 1, do we still do the feature
> > freeze? I don't want to be adding features after the freeze, that is
> [...]
> > As I remember, we decided that we should not make decisions to extend
>
On Thu, Apr 29, 2004 at 07:34:47PM +0100, Simon Riggs wrote:
> Bruce is correct, the API waits for the archive to be full before
> archiving.
>
> I had thought about the case for partial archiving: basically, if you
> want to archive in smaller chunks, make your log files smaller...this is
> now
On Thu, 29 Apr 2004, Bruce Momjian wrote:
> I wonder if we should just pick July 1 because there is good expectation
> based on current progress that Win32 will be done by June 15, which
> would be the next cuttoff date. Of course we can wait until May 15 and
> then decide.
Start of summer holid
Alvaro Herrera wrote:
> But a "savepoint" has a very precise meaning in the SQL standard,
> which relates to points in a transaction you can roll back to. I
> don't think you want to overload with this other meaning, which I see
> as putting a special mark in the XLog -- completely unrelated.
The
On Thu, 29 Apr 2004, Matthew T. O'Connor wrote:
> I know it's a chicken and egg problem, do we set a date for developers
> to shoot for, or do shoot for specific features and choose a date from
> there. I think there can no hard and fast rule on this, it depends on
> the feature and the desire to
On Thu, 29 Apr 2004, Bruce Momjian wrote:
> No. We tried that in the past and we ended up extending it in pieces
> several times. The effect was that we delayed feature freeze by a month
> or two, and other features never got developed in that timeframe. I
> remember SMP fixes for 7.3 as causing
On Thu, 29 Apr 2004, Bruce Momjian wrote:
> Merlin Moncure wrote:
> > Bruce Momjian wrote:
> > > Yes, it was vague. The question is now that we are a month away, do
> > we
> > > want to target June 1, mid-June, or July 1.
> >
> > If I may humbly chime in here...there currently is no binary packin
Bruce Momjian wrote:
> Well, if Win32 doesn't complete by June 1, do we still do the feature
> freeze? I don't want to be adding features after the freeze, that is
[...]
> As I remember, we decided that we should not make decisions to extend
> the feature freeze date just before the freeze date be
Matthew T. O'Connor wrote:
> Bruce Momjian wrote:
> > Well, if Win32 doesn't complete by June 1, do we still do the feature
> > freeze? I don't want to be adding features after the freeze, that is
> > for sure. When we have done that in the past, it has caused problems
> > because some stuff gets
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> Bruce Momjian wrote:
>> Yes, it was vague. The question is now that we are a month away, do
>> we want to target June 1, mid-June, or July 1.
> ... In short, speaking strictly from a win32
> perspective, a June 1 date will probably be missed.
Fair
Tom Lane wrote:
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
> > Bruce Momjian wrote:
> >> Yes, it was vague. The question is now that we are a month away, do
> >> we want to target June 1, mid-June, or July 1.
>
> > ... In short, speaking strictly from a win32
> > perspective, a June 1 date w
Andrew Sullivan wrote:
> On Thu, Apr 29, 2004 at 01:26:07PM -0400, Bruce Momjian wrote:
> > o nested transactions (Alvaro)
> >
> > Has submitted patches that are under review. He has the nesting of
> > BEGIN done, and storage manager subtransaction handling. I think he
> > needs to do pg_su
Bruce Momjian wrote:
Well, if Win32 doesn't complete by June 1, do we still do the feature
freeze? I don't want to be adding features after the freeze, that is
for sure. When we have done that in the past, it has caused problems
because some stuff gets in to make the system unstable, but other st
Simon Riggs wrote:
> > Also, I think this archiver should be able to log to a local drive,
> > network drive (trivial), tape drive, ftp, or use an external script to
> > transfer the logs somewhere. (ftp would probably be an external script
> > with 'expect').
>
> Bruce is correct, the API waits
Simon Riggs wrote:
On Thu, 2004-04-29 at 16:09, Peter Eisentraut wrote:
Perhaps that was the inspiration, but no, I definitely meant a
CHECKPOINT.
But now you come to mention it, it would be better just to have a
command that simply wrote a named record to the xlog, so it can
be searched for lat
On Thu, Apr 29, 2004 at 01:26:07PM -0400, Bruce Momjian wrote:
> o nested transactions (Alvaro)
>
> Has submitted patches that are under review. He has the nesting of
> BEGIN done, and storage manager subtransaction handling. I think he
> needs to do pg_subtrans system table and error recov
Merlin Moncure wrote:
> Bruce Momjian wrote:
> > Yes, it was vague. The question is now that we are a month away, do
> we
> > want to target June 1, mid-June, or July 1.
>
> If I may humbly chime in here...there currently is no binary packing for
> the win32 port. Magnus is currently working on
Marc G. Fournier wrote:
> On Thu, 29 Apr 2004, Bruce Momjian wrote:
>
> > Andrew Dunstan wrote:
> > > Marc G. Fournier wrote:
> > >
> > > >Right now, the feature freeze is tentative for 1st of June, which has been
> > > >thrown around a few times already ...
> > > >
> > > >
> > > >
> > >
> > > If
On Thu, 2004-04-29 at 15:22, Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > On Thu, Apr 29, 2004 at 10:07:01AM -0400, Bruce Momjian wrote:
> > > Alvaro Herrera wrote:
> >
> > > > Is the API able to indicate a written but not-yet-filled WAL segment?
> > > > So an archiver could copy the filled pa
On Thu, 2004-04-29 at 16:09, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > I'd suggest extending the CHECKPOINT command so you can say:
> > CHECKPOINT
> > e.g. CHECKPOINT 'starting payroll Feb04';
> > (I'm sure some other DBMS does this...head spinning can;t recall...)
> > the text could just a
On Thu, 29 Apr 2004, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> > Marc G. Fournier wrote:
> >
> > >Right now, the feature freeze is tentative for 1st of June, which has been
> > >thrown around a few times already ...
> > >
> > >
> > >
> >
> > If it has I've missed it - always seemed somewhat v
Bruce Momjian wrote:
> Yes, it was vague. The question is now that we are a month away, do
we
> want to target June 1, mid-June, or July 1.
If I may humbly chime in here...there currently is no binary packing for
the win32 port. Magnus is currently working on an installer/service
manager (dubbed
Matthew T. O'Connor wrote:
> Bruce Momjian wrote:
>
> > Yes, it was vague. The question is now that we are a month away, do we
> > want to target June 1, mid-June, or July 1.
> >
> > Some are saying that once Win32 is ready, it will justify a release even
> > if the other features are not ready.
On Thu, Apr 29, 2004 at 05:09:19PM +0200, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > I'd suggest extending the CHECKPOINT command so you can say:
> > CHECKPOINT
> > e.g. CHECKPOINT 'starting payroll Feb04';
> > (I'm sure some other DBMS does this...head spinning can;t recall...)
> > the text
Bruce Momjian wrote:
Yes, it was vague. The question is now that we are a month away, do we
want to target June 1, mid-June, or July 1.
Some are saying that once Win32 is ready, it will justify a release even
if the other features are not ready.
I think we should have this conversation once the wi
Andrew Dunstan wrote:
> Marc G. Fournier wrote:
>
> >Right now, the feature freeze is tentative for 1st of June, which has been
> >thrown around a few times already ...
> >
> >
> >
>
> If it has I've missed it - always seemed somewhat vaguer to me.
Yes, it was vague. The question is now that
Marc G. Fournier wrote:
> On Thu, 29 Apr 2004, Andrew Dunstan wrote:
>
> > Tom Lane said:
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > >> What we really need is for these folks to start finalizing their
> > >> patches and get them submitted.
> > >
> > > Eggzackle ... my point is that I see
On Mon, 26 Apr 2004 08:08:16 -0700, Sailesh Krishnamurthy
<[EMAIL PROTECTED]> wrote:
> "A Bi-Level Bernoulli Scheme for Database Sampling"
> Peter Haas, Christian Koenig (SIGMOD 2004)
Does this apply to our problem? AFAIK with Bernoulli sampling you don't
know the sample size in advance.
Anyway
Marc G. Fournier wrote:
Right now, the feature freeze is tentative for 1st of June, which has been
thrown around a few times already ...
If it has I've missed it - always seemed somewhat vaguer to me.
Thanks
andrew
---(end of broadcast)---
TIP 8: e
On Thu, 29 Apr 2004, Andrew Dunstan wrote:
> Tom Lane said:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> What we really need is for these folks to start finalizing their
> >> patches and get them submitted.
> >
> > Eggzackle ... my point is that I see the win32 train leaving the
> > station
Simon Riggs wrote:
> I'd suggest extending the CHECKPOINT command so you can say:
> CHECKPOINT
> e.g. CHECKPOINT 'starting payroll Feb04';
> (I'm sure some other DBMS does this...head spinning can;t recall...)
> the text could just appear in the xlog record data packet...
I believe you are thinki
Andrew Dunstan wrote:
> Tom Lane said:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> What we really need is for these folks to start finalizing their
> >> patches and get them submitted.
> >
> > Eggzackle ... my point is that I see the win32 train leaving the
> > station pretty soon, and I don
Tom Lane said:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> What we really need is for these folks to start finalizing their
>> patches and get them submitted.
>
> Eggzackle ... my point is that I see the win32 train leaving the
> station pretty soon, and I don't see anyone else ready to get on b
Alvaro Herrera wrote:
> On Thu, Apr 29, 2004 at 10:07:01AM -0400, Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > Is the API able to indicate a written but not-yet-filled WAL segment?
> > > So an archiver could copy the filled part, and refill it later. This
> > > may be needed because a s
On Thu, Apr 29, 2004 at 10:07:01AM -0400, Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Is the API able to indicate a written but not-yet-filled WAL segment?
> > So an archiver could copy the filled part, and refill it later. This
> > may be needed because a segment could take a while to be fi
Alvaro Herrera wrote:
> On Thu, Apr 29, 2004 at 12:18:38AM -0400, Bruce Momjian wrote:
>
> > OK, I looked over the code. Basically it appears pg_arch is a
> > client-side program that copies files from pg_xlog to a specified
> > directory, and marks completion in a new pg_rlog directory.
> >
> >
On Thu, Apr 29, 2004 at 12:18:38AM -0400, Bruce Momjian wrote:
> OK, I looked over the code. Basically it appears pg_arch is a
> client-side program that copies files from pg_xlog to a specified
> directory, and marks completion in a new pg_rlog directory.
>
> The driving part of the program see
hello,everyone! I want to know how postgresql remain its unique index unique after i have change it.For example: create table human(age int,name char(2));then in the pg_attribute catalog the unique index pg_attribute_relid_attnum_index willuse relid of 'human'and attnum of age to create a index tup
72 matches
Mail list logo
