pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedPresentation
13+ messages / 6 participants
[nested] [flat]
* Presentation
@ 2003-10-08 15:02 Jeff <threshar@torgo.978.org>
0 siblings, 4 replies; 13+ messages in thread
From: Jeff @ 2003-10-08 15:02 UTC (permalink / raw)
To: pgsql-performance
The boss cleared my de-company info-ified pg presentation.
It deals with PG features, crude comparison to other dbs, install, admin,
and most importantly - optimization & quirks.
Its avail in powerpoint and (ugg) powerpoint exported html.
Let me know if there are blatant errors, etc in there.
Maybe even slightly more subtle blatant errors :)
The people here thought it was good.
http://postgres.jefftrout.com/
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 15:51 Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
parent: Jeff <threshar@torgo.978.org>
3 siblings, 4 replies; 13+ messages in thread
From: Shridhar Daithankar @ 2003-10-08 15:51 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; +Cc: pgsql-performance
Jeff wrote:
> Let me know if there are blatant errors, etc in there.
> Maybe even slightly more subtle blatant errors :)
Some minor nitpicks,
* Slide 5, postgresql already features 64 bit port. The sentence is slightly
confusing
* Same slide. IIRC postgresql always compresses bytea/varchar. Not too much sure
about which but there is something that is compressed by default..:-)
* Tablespaces has a patch floating somewhere. IIRC Gavin Sherry is the one who
is most ahead of it. For all goodness, they will feature in 7.5 and design is
done. There aren't much issues there.
* Mysql transaction breaks down if tables from different table types are involved.
* Mysql transactions do not feature constant time commit/rollback like
postgresql. The time to rollback depends upon size of transaction
* Mysql does not split large files in segments the way postgresql do. Try
storing 60GB of data in single mysql table.
* Slide on informix. It would be better if you mention what database you were
using on your pentium. Assuming postgresql is fine, but being specific helps.
* Slide on caching. Postgresql can use 7000MB of caching. Important part is it
does not lock that memory in it's own process space. OS can move around buffer
cache but not memory space of an application.
* Installation slide. We can do without 'yada' for being formal, right..:-)
(Sorry if thats too nitpicky but couldn't help it..:-))
* initdb could be coupled with configure/make install but again, it's a matter
of choice.
* Slide on configuration. 'Reliable DB corruption' is a confusing term. 'DB
corruption for sure' or something on that line would be more appropriate
especially if presentation is read in documentation form and not explained in a
live session. but you decide.
* I doubt pg_autovacuum will be in core source but predicting that long is
always risky..:-)
* Using trigger for maintening a row count would generate as much dead rows as
you wanted to avoid in first place..:-)
All of them are really minor. It's a very well done presentation but 45 slides
could be bit too much at a time. I suggest splitting the presentation in 3.
Intro and comparison, features, administration, programming and tuning. Wow..
they are 5..:-)
Can you rip out informix migration? It could be a good guide by itself.
Thanks again for documentation. After you decide what license you want to
release it under, the team can put it on techdocs.postgresql.org..
Again, thanks for a good presentation..
Shridhar
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 15:59 Rod Taylor <rbt@rbt.ca>
parent: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
3 siblings, 0 replies; 13+ messages in thread
From: Rod Taylor @ 2003-10-08 15:59 UTC (permalink / raw)
To: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>; +Cc: Jeff <threshar@torgo.978.org>; pgsql-performance
> * Same slide. IIRC postgresql always compresses bytea/varchar. Not too much sure
> about which but there is something that is compressed by default..:-)
I'm not sure about that.
Even toasted values are not always compressed, though they certainly can
be and usually are.
Attachments:
signature.asc (application/pgp-signature, 186B) download
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 16:02 Josh Berkus <josh@agliodbs.com>
parent: Jeff <threshar@torgo.978.org>
3 siblings, 0 replies; 13+ messages in thread
From: Josh Berkus @ 2003-10-08 16:02 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; pgsql-performance
Jeff,
> Its avail in powerpoint and (ugg) powerpoint exported html.
I can probably convert it to OpenOffice.org and Flash. OK?
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [PERFORM] Presentation
@ 2003-10-08 16:05 Josh Berkus <josh@agliodbs.com>
parent: Jeff <threshar@torgo.978.org>
3 siblings, 0 replies; 13+ messages in thread
From: Josh Berkus @ 2003-10-08 16:05 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; pgsql-advocacy@postgresql.org
Jeff,
I'm jumping this thread to ADVOCACY, where it belongs, not PERFORMANCE.
> The boss cleared my de-company info-ified pg presentation.
> It deals with PG features, crude comparison to other dbs, install, admin,
> and most importantly - optimization & quirks.
>
> Its avail in powerpoint and (ugg) powerpoint exported html.
>
> Let me know if there are blatant errors, etc in there.
> Maybe even slightly more subtle blatant errors :)
>
> The people here thought it was good.
>
> http://postgres.jefftrout.com/
I'll check it out later today.
As I said in my e-mail, I'm happy to convert the format to something Open
Source. Can you release it under an OSS license?
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [PERFORM] Presentation
@ 2003-10-08 16:08 Josh Berkus <josh@agliodbs.com>
parent: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
3 siblings, 1 reply; 13+ messages in thread
From: Josh Berkus @ 2003-10-08 16:08 UTC (permalink / raw)
To: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>; +Cc: pgsql-advocacy@postgresql.org
Shridhar,
I'm jumping your reply to the proper mailing list. I have one comment at the
bottom; the rest of this quote is for the people on the Advocacy list.
> > Let me know if there are blatant errors, etc in there.
> > Maybe even slightly more subtle blatant errors :)
>
> Some minor nitpicks,
>
> * Slide 5, postgresql already features 64 bit port. The sentence is
> slightly confusing
> * Same slide. IIRC postgresql always compresses bytea/varchar. Not too much
> sure about which but there is something that is compressed by default..:-)
> * Tablespaces has a patch floating somewhere. IIRC Gavin Sherry is the one
> who is most ahead of it. For all goodness, they will feature in 7.5 and
> design is done. There aren't much issues there.
> * Mysql transaction breaks down if tables from different table types are
> involved. * Mysql transactions do not feature constant time commit/rollback
> like postgresql. The time to rollback depends upon size of transaction
> * Mysql does not split large files in segments the way postgresql do. Try
> storing 60GB of data in single mysql table.
> * Slide on informix. It would be better if you mention what database you
> were using on your pentium. Assuming postgresql is fine, but being specific
> helps. * Slide on caching. Postgresql can use 7000MB of caching. Important
> part is it does not lock that memory in it's own process space. OS can move
> around buffer cache but not memory space of an application.
> * Installation slide. We can do without 'yada' for being formal, right..:-)
> (Sorry if thats too nitpicky but couldn't help it..:-))
> * initdb could be coupled with configure/make install but again, it's a
> matter of choice.
> * Slide on configuration. 'Reliable DB corruption' is a confusing term. 'DB
> corruption for sure' or something on that line would be more appropriate
> especially if presentation is read in documentation form and not explained
> in a live session. but you decide.
> * I doubt pg_autovacuum will be in core source but predicting that long is
> always risky..:-)
> * Using trigger for maintening a row count would generate as much dead rows
> as you wanted to avoid in first place..:-)
>
> All of them are really minor. It's a very well done presentation but 45
> slides could be bit too much at a time. I suggest splitting the
> presentation in 3. Intro and comparison, features, administration,
> programming and tuning. Wow.. they are 5..:-)
>
> Can you rip out informix migration? It could be a good guide by itself.
>
> Thanks again for documentation. After you decide what license you want to
> release it under, the team can put it on techdocs.postgresql.org..
I'd suggest just having him release it under an OSS license now. That way,
you can make the corrections yourself, and we can convert it to OOo and Flash
and offer it in a variety of configurations.
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [PERFORM] Presentation
@ 2003-10-08 16:13 Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
parent: Josh Berkus <josh@agliodbs.com>
0 siblings, 0 replies; 13+ messages in thread
From: Shridhar Daithankar @ 2003-10-08 16:13 UTC (permalink / raw)
To: ; +Cc: pgsql-advocacy@postgresql.org
Josh Berkus wrote:
> Shridhar,
>
> I'm jumping your reply to the proper mailing list. I have one comment at the
> bottom; the rest of this quote is for the people on the Advocacy list.
> I'd suggest just having him release it under an OSS license now. That way,
> you can make the corrections yourself, and we can convert it to OOo and Flash
> and offer it in a variety of configurations.
Yeah. I read the request. After he does that, I could take some time off to
conevrt it. Long time since I have actually done on postgresql other than posts
on mailing list but.. anyways..
Sorry I should have put that on advocacy.. got left out..
Shridhar
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 16:27 Jeff <threshar@torgo.978.org>
parent: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
3 siblings, 0 replies; 13+ messages in thread
From: Jeff @ 2003-10-08 16:27 UTC (permalink / raw)
To: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>; +Cc: pgsql-performance
On Wed, 8 Oct 2003, Shridhar Daithankar wrote:
Thanks for the nitpicks :)
I've taken some into consideration.
I also signed onto the advocacy list so I can be in on discussions there.
Feel free to convert to whatever format you'd like. I originally started
working on it in OpenOffice, but I got mad at it. So I switched to
powerpoint and got mad at that too :)
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 17:05 Jeff <threshar@torgo.978.org>
parent: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
3 siblings, 0 replies; 13+ messages in thread
From: Jeff @ 2003-10-08 17:05 UTC (permalink / raw)
To: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>; +Cc: pgsql-performance
On Wed, 8 Oct 2003, Shridhar Daithankar wrote:
> * Same slide. IIRC postgresql always compresses bytea/varchar. Not too much sure
> about which but there is something that is compressed by default..:-)
> * Tablespaces has a patch floating somewhere. IIRC Gavin Sherry is the one who
> is most ahead of it. For all goodness, they will feature in 7.5 and design is
For the sake of things, I didn't include any features a patch provides. I
did include things that may appear in contrib/.
> * Mysql transaction breaks down if tables from different table types are involved.
> * Mysql transactions do not feature constant time commit/rollback like
> postgresql. The time to rollback depends upon size of transaction
> * Mysql does not split large files in segments the way postgresql do. Try
> storing 60GB of data in single mysql table.
I didn't add these ones. The user can figure this one out.
Perhaps when we/me expands this into multiple documents we can expand on
this.
> * Slide on caching. Postgresql can use 7000MB of caching. Important part is it
> does not lock that memory in it's own process space. OS can move around buffer
> cache but not memory space of an application.
I'm guilty of this myself - when I first started pg I was looking for a
way to make it use a zillion megs of memory like we have informix do -
Perhaps I'll reword that segment.. the point was to show PG relies on the
OS to do a lot of caching and that it doesn't do it itself.
> * Using trigger for maintening a row count would generate as much dead rows as
> you wanted to avoid in first place..:-)
We all know this.. but it is a way to get a fast select count(*) from
table
> All of them are really minor. It's a very well done presentation but 45 slides
> could be bit too much at a time. I suggest splitting the presentation in 3.
> Intro and comparison, features, administration, programming and tuning. Wow..
> they are 5..:-)
>
Yeah. What I'd really love to do is de-powerpointify it and make it a nice
set of "real" web pages.
> Can you rip out informix migration? It could be a good guide by itself.
>
I agree. It would be good to rip out. I think we have the oracle guide
somewhere..
I've put this updated on up on hte postgres.jefftrout.com site
along with openoffice version.
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 18:46 Neil Conway <neilc@samurai.com>
parent: Jeff <threshar@torgo.978.org>
3 siblings, 1 reply; 13+ messages in thread
From: Neil Conway @ 2003-10-08 18:46 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; +Cc: pgsql-performance
On Wed, 2003-10-08 at 11:02, Jeff wrote:
> The boss cleared my de-company info-ified pg presentation.
Slide 37: as far as I know, reordering of outer joins is not implemented
in 7.4
-Neil
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 19:38 Jeff <threshar@torgo.978.org>
parent: Neil Conway <neilc@samurai.com>
0 siblings, 2 replies; 13+ messages in thread
From: Jeff @ 2003-10-08 19:38 UTC (permalink / raw)
To: Neil Conway <neilc@samurai.com>; +Cc: pgsql-performance
On Wed, 8 Oct 2003, Neil Conway wrote:
> On Wed, 2003-10-08 at 11:02, Jeff wrote:
> > The boss cleared my de-company info-ified pg presentation.
>
> Slide 37: as far as I know, reordering of outer joins is not implemented
> in 7.4
>
Huh. I could have sworn Tom did something like that.
Perhaps I am thinking of something else.
You had to enable some magic GUC.
Maybe he did a test and it never made it in.
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 21:48 Neil Conway <neilc@samurai.com>
parent: Jeff <threshar@torgo.978.org>
1 sibling, 0 replies; 13+ messages in thread
From: Neil Conway @ 2003-10-08 21:48 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; +Cc: pgsql-performance
On Wed, 2003-10-08 at 15:38, Jeff wrote:
> Huh. I could have sworn Tom did something like that.
> Perhaps I am thinking of something else.
> You had to enable some magic GUC.
Perhaps you're thinking of the new GUC var join_collapse_limit, which is
related, but doesn't effect the reordering of outer joins.
-Neil
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Presentation
@ 2003-10-08 23:28 Tom Lane <tgl@sss.pgh.pa.us>
parent: Jeff <threshar@torgo.978.org>
1 sibling, 0 replies; 13+ messages in thread
From: Tom Lane @ 2003-10-08 23:28 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; +Cc: Neil Conway <neilc@samurai.com>; pgsql-performance
Jeff <threshar@torgo.978.org> writes:
> On Wed, 8 Oct 2003, Neil Conway wrote:
>> Slide 37: as far as I know, reordering of outer joins is not implemented
>> in 7.4
> Huh. I could have sworn Tom did something like that.
Not yet. 7.4 can reorder *inner* joins that happen to be written
with JOIN syntax.
regards, tom lane
^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2003-10-08 23:28 UTC | newest]
Thread overview: 13+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-10-08 15:02 Presentation Jeff <threshar@torgo.978.org>
2003-10-08 15:51 ` Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
2003-10-08 15:59 ` Rod Taylor <rbt@rbt.ca>
2003-10-08 16:08 ` Josh Berkus <josh@agliodbs.com>
2003-10-08 16:13 ` Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
2003-10-08 16:27 ` Jeff <threshar@torgo.978.org>
2003-10-08 17:05 ` Jeff <threshar@torgo.978.org>
2003-10-08 16:02 ` Josh Berkus <josh@agliodbs.com>
2003-10-08 16:05 ` Josh Berkus <josh@agliodbs.com>
2003-10-08 18:46 ` Neil Conway <neilc@samurai.com>
2003-10-08 19:38 ` Jeff <threshar@torgo.978.org>
2003-10-08 21:48 ` Neil Conway <neilc@samurai.com>
2003-10-08 23:28 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox