Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What is the point of such a distinction?
> If the contrib value is the source code itself then it seems a README is
> more appropriate as people are not going to install the contrib module
> itself --- they ar
is encouragement of people trying to
undo that change.
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
casts.
Please provide a concrete example.
> Should I be discussing this on a different list?
If you are looking for code changes, neither docs nor advocacy are
suitable forums.
regards, tom lane
---(end of broadcast)---
TIP 4
w)
but || not so much:
regression=# select 42 || 'foo';
ERROR: operator is not unique: integer || unknown
LINE 1: select 42 || 'foo';
^
HINT: Could not choose a best candidate operator. You might need to add
explicit type casts.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I think there's a case for putting these pages under Part V Server
>> Programming (though a few are not in fact server-side code), or under
>> Part VI Reference (ignoring the fact that most of the text
ks they're not of so much use anymore.
Thoughts?
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> Now that gborg.postgresql.org is officially dead, seems like it'd be a
>> good idea to update all the references to it that are in the FAQ.
>>
>> There are
ormalization*/) AS rank
Why is that correct (or more correct than other ways)?
> - Can we say what the differences are between the two ranking functions?
> Why do we have two?
We already say that: the _cd function doesn't work without positional
info in the input tsvector.
second example would be
SELECT title, ts_rank_cd(textsearch, query, 32 /* rank/(rank+1) */) AS rank
FROM apod, to_tsquery('neutrino|(dark & matter)') query
WHERE query @@ textsearch
ORDER BY rank DESC LIMIT 10;
with no change in the example output.
re
n behavior, if you fall foul of it.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ajor problem; and merely asserting that
it is one isn't going to change my mind. Can you point to something
like a major application that will be broken and can't easily be fixed?
regards, tom lane
---(end of broadcast)-
d practice:
both sides of the match should usually get normalized before comparison,
and these examples don't do that.
I'm not sure that putting in to_tsvector calls there would be an
improvement, though, since at that point we haven't introduced
to_tsvector.
Thoughts anyone?
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I'm not sure that putting in to_tsvector calls there would be an
>> improvement, though, since at that point we haven't introduced
>> to_tsvector.
>>
>> Thoughts anyone?
> Yep, I
s a bit better I think:
http://developer.postgresql.org/pgdocs/postgres/textsearch-intro.html#TEXTSEARCH-MATCHING
So the first thing is to go bug the www team about updating the online
8.3beta docs, which I shall do forthwith.
regards, tom lane
RNS SETOF sometype
you can't just say, eg,
RETURNS SET
Your new wording would lead the reader to the assumption that he can
just declare a function as returning "set".
Please revert the change.
regards, tom lane
---
eem like a good idea.
regards, tom lane
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
David Fetter <[EMAIL PROTECTED]> writes:
> On Wed, Nov 28, 2007 at 03:53:04PM -0500, Tom Lane wrote:
>> Entirely removing the example of how to do it with rules doesn't
>> seem like a good idea.
> It does to me. I haven't found a case yet where rules worked ev
David Fetter <[EMAIL PROTECTED]> writes:
> On Wed, Nov 28, 2007 at 09:58:26PM -0500, Jonah H. Harris wrote:
>> On Nov 28, 2007 3:53 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> Entirely removing the example of how to do it with rules doesn't
>>> seem lik
ce per row. Also, if you implement the trigger
with an EXECUTE (forcing a planning cycle) intead of hard-coded
commands, the speed advantage becomes even more dubious.
regards, tom lane
---(end of broadcast)---
TIP 7: You can he
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> A trigger
>> will probably beat a rule for inserts/updates involving a small number
>> of rows.
> Which is exactly what partitioning is doing.
Nonsense. Well, maybe *you* never do that
titioned tables where rules are being employed,
>> the COPY operation will not be so straightforward.
> Does my latest patch attached address this well enough?
Applied with revisions and extensions. (I take it you hadn't actually
tested the example :-()
re
Albert Cervera i Areny <[EMAIL PROTECTED]> writes:
> Attached, the dict_int and dict_xsyn SGML docs.
Applied, thanks.
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
on the contrib docs? I'm
interested in making an editorial pass over them in the next day or two,
but I don't want to create merge conflicts for you if you are about to
do more work.
regards, tom lane
---(end of broadcast)---
all the contrib modules.
Comments?
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
actice is that autocompletion fixes don't make the
release notes at all.
It might be worth reminding folks that the release notes do not
exist for the purpose of mentioning contributors.
regards, tom lane
---(end of broadcast)---
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It might be worth reminding folks that the release notes do not
>> exist for the purpose of mentioning contributors.
> Then why do we mention them at all in the release notes?
You've got th
ction to listing people on the contributors page
on the strength of their work on contrib modules. But that seems
orthogonal to the question of what should be in the SGML docs ...
regards, tom lane
---(end of broadcast)---
TIP 5: don&
Jeff Davis <[EMAIL PROTECTED]> writes:
> The lastval() function appears to be missing from table 9-38.
Fixed in CVS HEAD --- thanks for reporting it.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you sea
s that are wrong for this
purpose.
I spent a bit of time with a thesaurus but didn't come up with anything
that seemed le mot juste. Best I could do was "spread checkpoint"
or "time-extended checkpoint". Anybody have a better idea?
respond especially fast.
If the community-at-large can't handle a bug, we certainly have enough
institutional memory to try to contact the original author, even if that
address isn't in the SGML docs.
regards, tom lane
---(end of broa
you're mistaken. (Again, it's not so much the
hook itself that's the problem, as all the stuff that the hooked-in
function needs to know about.)
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
#x27;t know the DSSSL stuff well enough to know where to look.
Anyone want to tackle it?
(A workaround might be to suppress the list-of-tables in PDF output,
but I dunno how to do that either.)
regards, tom lane
---(end of broadcast)
#x27; is something up with which I will not put.
> On the other hand, maybe this conversion of ' to
> &apod; should be built into the xslt processing (to leave
> the sgml more readable)?
That would be tolerable.
regards, tom lane
--
f EXECUTE here; the performance implications are bad.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
x27;t represent the check
constraints that way (at least not if you want the planner to do
constraint exclusion with them) and I don't think it's "less
error-prone" to have a different representation in the trigger than
you have in the constraints.
regards,
t;make clean all" than to try to use the existing state.
I have not looked into why, but certainly this isn't very satisfactory.
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
tsvector column.)
Huh? These are just examples, they are not supposed to refer to any
specific real table, much less one that comes standard with Postgres.
regards, tom lane
---(end of broadcast)---
TIP 7: You can he
SELECT 'a:1 a:1'::tsvector;
tsvector
--
'a':1
(1 row)
regression=# SELECT 'a:1,2,1'::tsvector;
tsvector
--
'a':1,2
(1 row)
regards, tom lane
---(end of broadcast)---
TIP 9
msgid to be wrong, exactly; but if
you have a proposal for better wording, I'm all ears.
regards, tom lane
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
han bgwriter_lru_maxpages
buffers will be written per round.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Greg Smith <[EMAIL PROTECTED]> writes:
> On Sun, 20 Jan 2008, Tom Lane wrote:
>> I think the main problem is the qualifying clause up front in a place
>> of prominence. Here's a V3 try
> That one looks good to me. These are small details but better to get it
>
"Erik" <[EMAIL PROTECTED]> writes:
> Can these occurrences of 'PgAccess' be replaced by 'PgAdmin'?
Done. I notice that some of the non-English FAQ translations still
mention PgAccess, but I'll leave it to Bruce to worry about those ..
iles in OBJS".
Are we really in the business of teaching C programmers the difference
between object files and shared libraries?
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our l
s worth a paragraph.
But we have only *one* report. Furthermore, there is no reason to think
that the symptoms are consistent across platforms or PG versions, so
I don't even know what the paragraph should say.
regards, tom lane
---(end of broa
e should remove
the section, since it gives some indication of which other platforms
have been known to work in the past (and likely will still work, despite
the lack of an active buildfarm member).
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
ntation.
PQsetClientEncoding seems to be documented in the wrong place.
As for the expbuffer stuff, that is intentionally not considered part of
libpq's exported API. If someone uses it, they get to keep both parts
when it breaks.
regards, tom lane
--
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> PQinitSSL *is* documented, though looking at the para immediately raises
>> the question what the heck we are doing pointing to a random hp.com page
>> for SSL documentation.
> I added that for 8.3
a few other platforms that are similarly
used by other key developers --- I don't see any indication that Bruce
is running a buildfarm member on whichever-BSD-he-uses, for instance.
regards, tom lane
---(end of broadcast)--
; referring to. I don't know what HP has to do with it.
Yeah, I was thinking a simple pointer to www.openssl.org would be more
appropriate. We're not here to substitute for somebody doing their
own Google search ...
regards, tom lane
---(
I've replaced the section with the
attached text.
regards, tom lane
Supported Platforms
A platform (that is, a CPU architecture and operating system combination)
is considered supported by the PostgreSQL development
community if the code contains
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> The main problem with using the link as it stands is that it is *highly*
>> unlikely that it will remain valid for the lifespan of the PG 8.3
>> documentation (let alone subsequent versions). I've
on), and if there is any question about the
legality then that's just frosting on the cake.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
"Gurjeet Singh" <[EMAIL PROTECTED]> writes:
> http://www.postgresql.org/docs/8.2/interactive/indexes-opclass.html
> The examples given at the end of this page do not work in 8.2.4.
They work fine for me ...
regards, tom lane
--
Decibel! <[EMAIL PROTECTED]> writes:
> On Fri, Jan 04, 2008 at 12:25:59PM -0500, Tom Lane wrote:
>> That won't actually work.
> I think it's still worthy as an example.
I think what we have here is a failure to communicate. How are you
going to do performance measur
e able to say anything very
specific. Another problem is where would you put the information?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-docs
hing on that list would be mysql.
If we need a FAQ entry on this at all, I'd stop after David's first two
sentences.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-docs
David Fetter <[EMAIL PROTECTED]> writes:
> On Wed, Mar 05, 2008 at 12:35:53PM -0500, Tom Lane wrote:
>> If we need a FAQ entry on this at all, I'd stop after David's first
>> two sentences.
> Stopping there seems like a very bad idea from a public relation
cked into. Better not to go there in the first
place.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-docs
o control who-can-connect-where than setting up fancy combinations
of user and database entries in pg_hba.conf. AFAIR there is no mention
of this alternative in Chapter 21, but it seems like there ought to be.
With your proposed reorganization, that would become a forward
reference; is that OK?
its *contents* might not be up to date, but that shouldn't
affect pg_total_relation_size.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
t I'd expect. (The exact value
could vary across platforms, of course.)
You said you were using the MinGW build --- maybe MinGW's version
of stat(2) isn't trustworthy?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To
w if they
go that way.
Possibly the text should be reworded, with the mention of DBD::PgSPI put
somewhere else or stuck into a or something.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://w
+1 for just dropping the mention.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Simon Riggs <[EMAIL PROTECTED]> writes:
> I'm trying to add a new ref/.sgml file, but I can't see which file needs
> to change to allow that to be fully referenced.
Example:
$ grep psqlRef *sgml ref/*sgml
reference.sgml: &psqlRef;
ref/allfiles.sgml:
$
cond part of the filename can ordinarily
be ignored. I don't know why neither he nor you managed to parse the
sentence correctly. Feel free to propose a rewording, but removing
information doesn't sound like a solution.
regards, tom lane
--
Sent via
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> But in my freshly 8.3.1 instalation on win xp, the default is
> "fsync"... is a *bug* in the docs :)
More like a bug in the code. Does it let you set the value to
open_datasync?
regards, t
I am wondering whether to leave the release note pages for 8.3.2, 8.2.8,
etc saying "Release date: 2008-06-09", or to change them to something
like "Never released". Thoughts?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@pos
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I am wondering whether to leave the release note pages for 8.3.2, 8.2.8,
>> etc saying "Release date: 2008-06-09", or to change them to something
>> like "Never released". Thoughts?
! TeX capacity exceeded, sorry [hash size=6].
...
Here is how much of TeX's memory you used:
...
6 multiletter control sequences out of 1+5
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your
we
> should put this with the aggregate functions or the XML functions, or both,
> in some way. Any ideas?
It doesn't seem to fit with the other aggregate functions, so I think
I'd vote for documenting it with the XML functions.
regards, tom lane
--
Sen
Robert Treat <[EMAIL PROTECTED]> writes:
> On Saturday 07 June 2008 13:02:57 Tom Lane wrote:
>> I am wondering whether to leave the release note pages for 8.3.2, 8.2.8,
>> etc saying "Release date: 2008-06-09", or to change them to something
>> like "Nev
s fired
> on INSERT on a view can do the same as a rule".
This was discussed last month:
http://archives.postgresql.org/pgsql-general/2008-06/msg00669.php
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make cha
gree it's not entirely obvious that what it
means is "multiply your setting in KB/MB by 8400/8192". Anybody have
an idea how to clarify things?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
nalyze stats will result in invalidating any cached
plans. So the system should be capable of auto-tuning its plans to
changes in table size ... not instantaneously of course, but then you
can't fill a big table instantaneously either.
regards, tom lane
--
Sent via pgsql
be written in
>
> probably must be:
> ...
>
> identifier
> length
>
>
> The system uses no more than NAMEDATALEN-1
> bytes of an identifier; longer names can be written in
> ...
> What you think?
AFAICS it's fine as-is.
ns. It might look a bit overloaded then.
> Comments?
Perhaps the most useful thing would be to keep SQL-92 and latest, so
as to show the "full range" in what's been reserved or not in different
spec revisions.
regards, tom lane
--
Sent via
r that. Are other modules similarly affected?
> We don't have names in any of the other chapters, so perhaps we should
> remove all the names?
This was discussed before and got some push-back:
http://archives.postgresql.org/pgsql-docs/2007-12/msg00012.php
re
it would suggest we are
> talking about objects and not bytes.
I'm with Alvaro: neither of those changes were improvements.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
ries, while chapter 17 deals with system configuration issues.
These should be kept separate, because in the common case of using
a prepackaged build, chapter 15 is of no interest but 17 still is.
It's quite likely that some of the stuff extracted from the old platform
FAQs really belongs in 17.
(1800 + 270 * max_locks_per_transaction) * (max_connections +
autovacuum_max_workers)
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Bruce Momjian writes:
> Tom Lane wrote:
>> If you're going to give a formula, why not just give a formula, eg
> You mean like this:
> http://momjian.us/tmp/pgsql/kernel-resources.html
Yeah, more or less. A couple thoughts now that I see it worked out:
* Combi
Bruce Momjian writes:
> Tom Lane wrote:
>> * If we do it like this then the left-hand column is really redundant,
>> not to say wrong because the right-hand formulas depend on more than
>> the single variable mentioned. How about something like
>>
>> Table 17-2
t sense that we simply
stopped updating back branches' FAQs (which hardly seems ideal). So
losing it doesn't seem like a showstopper objection to me. Still, it's
something that might be nice to preserve if we can.
regards, tom lane
--
Sent via pgsql-docs ma
king point would be about how long to preserve FAQ
entries that are no longer relevant to the current release.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Frank Wiles writes:
> Attached is a patch that makes the suggestion be 'rsync -avr' in both
> backup.sgml and pg_standby.sgml.
Seems to me the first question to ask is exactly why you got "bit" by
cp. I doubt that rsync will provide a magic answer.
; http://developer.postgresql.org/pgdocs/postgres/datatype.html
That is a chapter heading, not a section heading.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Mario Splivalo writes:
> Hope this is ok. How can I submit patch for 8.3 documentation?
I think you just did. Applied, thanks.
regards, tom lane
PS: why'd you omit unnest()?
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes
;re all laid out by hand :-(
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
#x27;t even work; did you test uncommenting that?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
it is ms
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
for people to know what the underlying
variable's unit is? I certainly think that putting the unit info into
the text descriptions is a seriously bad idea. It makes an already
overly wide view even wider, and the information is 100% redundant with
the "unit" column of the pg_settings view
Bruce Momjian writes:
> Tom Lane wrote:
>> You know, it suddenly strikes me that this is going in largely the wrong
>> direction.
> Right, the problem particularly is with the -1/special values that don't
> have a real unit.
I don't object to what you did to post
Bruce Momjian writes:
> However, keep in mind that units are _not_ displayed for zero values:
Well, zero is zero, so that seems fine.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
h
Bruce Momjian writes:
> Did unnest() get added properly too?
Yes, I included it in the patch.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
, but how much are we really
saving? Four sentences out of our current docs doesn't excite me ...
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Scott Marlowe writes:
> On Mon, Apr 13, 2009 at 12:04 AM, Tom Lane wrote:
>> Pre-7.1 might indeed be old enough to cut, but how much are we really
>> saving? Four sentences out of our current docs doesn't excite me ...
> But since there's a doc set per version,
t is seen to
have the right type, eg
insert into person values ('Joe', array[row('1','')::phone,
row('2','2222')::phone]);
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make chang
ed in the release.sgml file, but that doesn't
change anymore in back branches so there's no risk of overwriting it.)
Thoughts?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
ng.
Couldn't the sentence be trimmed to just
The following functions return XML Schema documents describing the
mappings produced by the corresponding functions above.
If that phrasing is wrong for some reason, then I agree with Bruce that
the sentence needs a complete rewri
7;t be adequate either,
given that it won't change nearly as fast as the included files.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
301 - 400 of 948 matches
Mail list logo
