Patch applied. Thanks. Your documentation changes can be viewed in
five minutes using links on the developer's page,
http://www.postgresql.org/developer/testing.
---
Mark Kirkwood wrote:
> Bruce Momjian wrote:
> > Mark K
Robert Treat wrote:
> I thought it was more correct to use < rather than < inside of
> tags?
Using < is never allowed in "plain text".
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Have you searched
Robert Treat wrote:
> On Tuesday 15 February 2005 02:34, Mark Kirkwood wrote:
> > Bruce Momjian wrote:
> > > Mark Kirkwood wrote:
> > >>At Tom's suggestion, I am going to amend the page to fit into the
> > >>'internals' chapter as opposed to 'performance tips' one. I might do
> > >>this first, and
Robert Treat wrote:
I thought it was more correct to use < rather than < inside of
tags?
I am unsure about this myself (I copied the usage from perform.sgml).
Mark
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregis
On Tuesday 15 February 2005 02:34, Mark Kirkwood wrote:
> Bruce Momjian wrote:
> > Mark Kirkwood wrote:
> >>At Tom's suggestion, I am going to amend the page to fit into the
> >>'internals' chapter as opposed to 'performance tips' one. I might do
> >>this first, and send you the resulting page.
> >
Bruce Momjian wrote:
Mark Kirkwood wrote:
At Tom's suggestion, I am going to amend the page to fit into the
'internals' chapter as opposed to 'performance tips' one. I might do
this first, and send you the resulting page.
That sounds good, that this become part of the developer docs.
Here is the
Mark Kirkwood wrote:
> Josh Berkus wrote:
> >
> > Or plain text, if that's easier.
> >
>
> Probably the easiest way is for me to generate the sgml -> html and send
> you that. It would look like a Pg docs html page. I guess the header and
> heading information might need a bit of editing (if it i
Josh Berkus wrote:
Or plain text, if that's easier.
Probably the easiest way is for me to generate the sgml -> html and send
you that. It would look like a Pg docs html page. I guess the header and
heading information might need a bit of editing (if it is obvious what
should be removed I will do th
Mark, Mike,
Yeah, right, powerpostgresql.com
> Absolutely, that is an excellent spot for it, do you need it reformatted
> in html first?
Or plain text, if that's easier.
> BTW - in fact a community site may well be more appropriate for it than
> the docs, as someone has to remember to change it
Josh Berkus wrote:
Mark,
Terrific. I'd be happy to post this at www.powerpostgresql.org, if you want;
I think a lot of people would be interested.
Absolutely, that is an excellent spot for it, do you need it reformatted
in html first?
BTW - in fact a community site may well be more appropriat
On Sat, Feb 12, 2005 at 03:22:10PM -0800, Josh Berkus wrote:
>
> Terrific. I'd be happy to post this at www.powerpostgresql.org, if you
> want;
Shouldn't that be www.powerpostgresql.com?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)--
Mark,
> > I wanted to understand how the planner 'knows' how many rows are likely
> > to be emitted in a given stage of a query, and wrote down some examples
> > for my own benefit - I then wondered if this would be a good addition to
> > the 'Performance Tips' chapter. So... err here it is.
> >
>
Post feedback changes - thanks to all who commented!
Mark Kirkwood wrote:
I wanted to understand how the planner 'knows' how many rows are likely
to be emitted in a given stage of a query, and wrote down some examples
for my own benefit - I then wondered if this would be a good addition to
the 'Per
I wanted to understand how the planner 'knows' how many rows are likely
to be emitted in a given stage of a query, and wrote down some examples
for my own benefit - I then wondered if this would be a good addition to
the 'Performance Tips' chapter. So... err here it is.
Comments welcome.
best wishe
14 matches
Mail list logo
