Bruce Momjian wrote:
pgman wrote:
I have marged Tom's description of the new sequence binding with text I
was working on. I modified it to follow the existing "we used to do X,
now we do Y" pattern in the surrounding entries:
http://candle.pha.pa.us/tmp/pgsql/release.html#RELEASE-8-1
Sorry,
Tom Lane <[EMAIL PROTECTED]> writes:
> Here's another interesting case to think about:
>
> ALTER TABLE ADD foo integer DEFAULT 1
> ...
> ALTER TABLE ALTER foo SET DEFAULT 2
>
> You'll have to pay the table-traversal cost on one step or the other.
A good point.
I wonder if thi
On Mon, Oct 03, 2005 at 02:16:37AM +0200, Andreas Pflug wrote:
> In-time for PostgreSQL 8.1 gold, The pgAdmin Developer Team will
> release pgAdmin III V1.4, which has a new Guru hint feature that
> tries to give users helpful hints on typical beginner's pitfalls.
>
> The current set of hints is a
Bruce Momjian writes:
> Jim C. Nasby wrote:
>> Watching the discussion about how to handle nextval() and keep it dump
>> compatible makes me wonder: would it be useful to encode database or
>> dump version info into dumps?
> If we ever get to a case where we _need_ to use it, it would be good to
Jim C. Nasby wrote:
> Watching the discussion about how to handle nextval() and keep it dump
> compatible makes me wonder: would it be useful to encode database or
> dump version info into dumps? ISTM it would make it much more feasible
> to handle changes to how things work automatically.
Yes, we
Greg Stark <[EMAIL PROTECTED]> writes:
> It would be nice to be able to do:
> ALTER TABLE ADD foo integer DEFAULT 1
> And there's no question of what what the semantics of this are.
Sure, but you can only optimize this if the default expression is
immutable...
> On the other hand if you do
> A
pgman wrote:
> I have marged Tom's description of the new sequence binding with text I
> was working on. I modified it to follow the existing "we used to do X,
> now we do Y" pattern in the surrounding entries:
>
> http://candle.pha.pa.us/tmp/pgsql/release.html#RELEASE-8-1
Sorry, this is a
Martijn van Oosterhout writes:
> On Sun, Oct 02, 2005 at 11:51:27PM +0300, Hannu Krosing wrote:
> > Right. Actually the "default" value returned for missing columns should
> > be different from the default for new values and should be settable only
> > once, when adding the column, else issues wo
I have marged Tom's description of the new sequence binding with text I
was working on. I modified it to follow the existing "we used to do X,
now we do Y" pattern in the surrounding entries:
http://candle.pha.pa.us/tmp/pgsql/release.html#RELEASE-8-1
I also added an SQL query that will s
Core's current plan is to wrap update releases for 8.0, 7.4, 7.3
branches tomorrow (Monday evening North-American-east-coast time).
If you're aware of any critical open problems in those branches,
speak now ...
regards, tom lane
---(end of broadcast
Fredrik Olsson <[EMAIL PROTECTED]> writes:
> To allow indexes to be inherited so unique, foreign keys and such works
> properly with inheritance has been on the todo for quite some time. I
> thought that most probably it is a very non trivial thing, perhaps
> completely rethinking how indexes ar
Watching the discussion about how to handle nextval() and keep it dump
compatible makes me wonder: would it be useful to encode database or
dump version info into dumps? ISTM it would make it much more feasible
to handle changes to how things work automatically.
--
Jim C. Nasby, Sr. Engineering Co
In-time for PostgreSQL 8.1 gold, The pgAdmin Developer Team will release
pgAdmin III V1.4, which has a new Guru hint feature that tries to give
users helpful hints on typical beginner's pitfalls.
The current set of hints is at
http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/trunk/pgadmin3/docs/en_US
Hi.
To allow indexes to be inherited so unique, foreign keys and such works
properly with inheritance has been on the todo for quite some time. I
thought that most probably it is a very non trivial thing, perhaps
completely rethinking how indexes are done. Or perhaps it is not a
feature that
On P, 2005-10-02 at 15:30 +0200, Martijn van Oosterhout wrote:
> On Sun, Oct 02, 2005 at 03:57:37PM +0300, Hannu Krosing wrote:
> > On P, 2005-10-02 at 01:24 -0400, Greg Stark wrote:
> > > Of course that only works if the reason they want to set fill the rows
> > > with
> > > the default value isn
On Sun, Oct 02, 2005 at 11:51:27PM +0300, Hannu Krosing wrote:
> Right. Actually the "default" value returned for missing columns should
> be different from the default for new values and should be settable only
> once, when adding the column, else issues would become really really
> weird.
Right,
If one defines a restriction such that 'COLUMN = VALUE' for a specific
table, in a theoretical sort of model that completely ignores
implementation difficulty, or changes to the restriction, I think it
would be safe to not store COLUMN in the tuple. If the tuple is
stored, then COLUMN = VALUE, so w
The following patch implements a fairly light set of timing statements
aimed at understanding external sort performance. There is no attempt to
alter the algorithms.
Each major point in the algorithms is marked as shown in this example:
postgres=# set debug_sort=true;
SET
postgres=# explain anal
Ok, I tried two optimisations:
1. By creating a special version of comparetup_index for single key
integer indexes. Create an index_get_attr with byval and len args. By
using fetch_att and specifying the values at compile time, gcc
optimises the whole call to about 12 instructions of assembly rath
On Sun, 2005-10-02 at 19:43 +0100, Simon Riggs wrote:
> The following patch implements a fairly light set of timing statements
> aimed at understanding external sort performance. There is no attempt to
> alter the algorithms.
Minor update of patch, use this version please.
> Best Regards, Simon R
Martijn van Oosterhout writes:
> However, from a semantic point of view, it would be a bit strange. If
> you added a column, updated some rows then set a default, that default
> might end up applying to every row, except the ones you already
> modified. With careful coding you may be able to get
On Sun, Oct 02, 2005 at 12:20:05PM +0200, Thomas Hallgren wrote:
> I added some traces to the code. I know that the following happens when
> I start a postmaster.
> In the second iteration of ServerLoop, pgstat_forkexec will again call
> will call internal_fork_exec. This time it fails.
> Acc
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] pgsqldev]$ bin/pg_dumpall -U jd -D -o -p 5500
> ...
> pg_dump: INSERT (-d, -D) and OID (-o) options cannot be used together
> pg_dump: (The INSERT command cannot set OIDs.)
> pg_dumpall: pg_dump failed on database "postgres", exiting
On Sun, Oct 02, 2005 at 03:57:37PM +0300, Hannu Krosing wrote:
> On P, 2005-10-02 at 01:24 -0400, Greg Stark wrote:
> > Of course that only works if the reason they want to set fill the rows with
> > the default value isn't precisely because NULL is a perfectly reasonable
> > thing
> > for the col
On P, 2005-10-02 at 01:24 -0400, Greg Stark wrote:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
>
> > I also often wish that this would be possible when someone adds a column
> > with a default value to a multi-million row table on a 24/7 production
> > system and insists on filling all existing co
On Sat, Oct 01, 2005 at 11:26:07PM -0400, Tom Lane wrote:
> Martijn van Oosterhout writes:
> > Anyway, to bring some real info I just profiled PostgreSQL 8.1beta
> > doing an index create on a 2960296 row table (3 columns, table size
> > 317MB).
>
> 3 columns in the index you mean? What were the
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jim C. Nasby
> Sent: Friday, September 30, 2005 4:49 PM
> Subject: Re: [PERFORM] [HACKERS] Query in SQL statement
> I suggest ditching the CamelCase and going with underline_seperators.
> I'd also not use
I added some traces to the code. I know that the following happens when
I start a postmaster.
StartupDatabase will call internal_fork_exec, it calls
write_inheritable_socket 4 times and succeeds.
During the first iteration of ServerLoop:
StartBackgroundWriter will call internal_fork_exec and
On Sat, Oct 01, 2005 at 04:35:49PM +0200, Martijn van Oosterhout wrote:
> On Sat, Oct 01, 2005 at 10:05:22AM -0400, [EMAIL PROTECTED] wrote:
> > It has the 'side or additional benefit' being requested here. The ability
> > to filter the child table by some attribute. For example, if the child
> > t
Martijn van Oosterhout wrote:
On Thu, Sep 29, 2005 at 08:50:30AM +0200, Thomas Hallgren wrote:
Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my Windows-XP box.
It runs fine but I get repeated messages like this in the log:
2005-09-29 00:41:09 FATAL: could not duplicate socket
30 matches
Mail list logo
