what we have at
the moment.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
o any particular version then you should
just say "SQL", anyhow.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
m not sure how hard that is though.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
"Wood, Bruce" <[EMAIL PROTECTED]> writes:
> There is an error in your example for the prepare statement on page
> http://developer.postgresql.org/docs/postgres/sql-prepare.html.
Good catch --- none of those quotes should be there. Thanks.
oss-reference in the
array functions section, but we shouldn't list array() as though it were
just like every other function in the section.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore yo
ying he doesn't like the current
categorization, or that he doesn't believe in the idea at all.
But I don't think "one big list" will fly.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
ix.
Yeah, I think you're right. Change made.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
real lack in this section is examples to clarify the
implications of the rules, and you haven't added any ... in fact it
looks like you removed the examples that were there.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
ction to suggest that LIKE performance
might be affected. A para in the "Locale Support" section (in
charset.sgml) would probably be appropriate, and maybe another word or
two in the place that link to it in runtime.sgml and ref/initdb.sgml.
regards, tom lane
--
Mark Kirkwood <[EMAIL PROTECTED]> writes:
> I am seeing a docs build failure :
Fixed, thanks. (You must be running a pickier version of docbook
than is installed at postgresql.org ...)
regards, tom lane
---(end of
far as the
markup correctness is concerned, better tighter than looser.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
hing than of giving
recipes.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
o one's really stepped
up to do the writing. If you want to give it a go, by all means ...
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
lly comparing it to our
present theory about Joe Conway's recent troubles. That is, I wonder
if he had a mistakenly-reinitialized pg_control.
Harry, are you using a Postgres start script that will automatically
run initdb if it doesn't see a valid data directory at $PGDATA?
even still need the "Installation on Windows" section? Is
anyone still going to care about building the frontend tools that way?
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase
Bruce Momjian writes:
> Oh, I see this needs some major restructuring/relabeling. I am working
> on that now.
I'm already in process of copy-editing that file; please don't change it
under me.
regards, tom lane
---(
ansposed into that chapter?
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Bruce Momjian writes:
> Oops. I just committed. I will back it out. Let me know when you are
> done.
Never mind then, I'll merge ...
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
OK, I'm out of installation.sgml if you want to have another hack at it.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "
;s in the wrong place. I am not sure what the right place is though.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's dataty
Bruce Momjian writes:
> Tom Lane wrote:
>> At the bottom of
>> http://developer.postgresql.org/docs/postgres/install-win32.html
>> there is some info about having to set the correct console code page
>> for psql. Does this apply to the MinGW and/or Cygwin builds, or
f tempted to add it to the Preface.
Thoughts?
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I'm pretty well convinced that the new docs chapter "External Projects"
>> does not belong under the Client Interfaces volume.
> It seems that it should be broken up by the type of
Bruce Momjian writes:
> Tom Lane wrote:
>> I'm about half tempted to add it to the Preface.
> The Preface would be OK if it didn't have so much client-interface
> specific stuff in it. I wonder if Appendix is best, with a pointer to
> the appendix at the end of the
Honda Shigehiro <[EMAIL PROTECTED]> writes:
> A word "table" in SQL "INSERT INTO table VALUES (3);" is reserved.
> So renaming or quoting are needed to avoid an error.
Fixed, thanks.
regards, tom lane
the default value, which is not implemented yet.
Drat, I thought I'd caught all those. Thanks.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
wrong here?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
tion whatsoever to the
documentation HTML files, it's broken. I don't think the above fix
is appropriate --- what if the docs contain {foo} where foo does match
some variable known to the substituter?
regards, tom lane
---(end of broadc
Bruce Momjian writes:
> Should the doc tarball contain the manual pages? Right now it does not.
> It only has the SGML files in HTML.
What? The man pages are in man.tar.gz.
regards, tom lane
---(end of broadcast)-
these forms still work:
http://www.postgresql.org/docs/8.0/static/
http://www.postgresql.org/docs/current/static/
"current" has always been just a symlink to the active version number.
regards, tom lane
---(end of broadcast)--
s surely obsolete, anyway.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ckhart is doubtless
responsible for it being in our code; I suppose he put it in because it
is in reasonably common use at JPL.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
eps (such as loading data into the table) isn't supported, but
pointing that out in the rules discussion seems like distracting
pedantism, rather than information that's helpful right at that point.
Can you think of another place it'd be worth mentioning?
explains all that in
detail.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
s pg_dump wants to lock the table.
Huh? pg_dump only takes ACCESS SHARE lock, which requires only SELECT
privileges.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archive
reeBSD entry before the
other two, not after, so maybe that should be "see below".
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
y OK English grammar to me.
What change are you suggesting exactly?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
good thing,
since it applies to more than one platform.
> ii) we are recommending setting kernel.shmall equal to kernel.shmmax. I
> think this is incorrect or strange anyway :
It does make sense for shmall-in-bytes to exceed shmmax-in-bytes, but
probably not by a factor of 4000 ...
ving average under 8.0.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
syntax for
.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
greSQL would want to know this.
The release notes cover that; or you can compare the docs for the oldest
and newest versions you want to work with. I think it would be more
confusing than helpful for the reference pages to try to cover all the
changes from version to v
David Fetter <[EMAIL PROTECTED]> writes:
> Please find a patch per IRC chat yesterday that clarifies how much
> space a NUMERIC takes.
Applied with minor editorialization.
regards, tom lane
---(end of broadcast)-
Jeff - <[EMAIL PROTECTED]> writes:
> Eventually we found it was SELinux was preventing pg_dump from
> producing output.
That's a new one on me. Why was it doing that --- mislabeling on
the pg_dump executable, or what?
regards, tom lane
--
eve the problems are all resolved in the latest Fedora RPMs,
though this pg_dump report may be something new.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(s
ere too, because I've noticed cases where an action was
blocked and there wasn't any log message, nor enough activity to
justify a rate limit. Feel free to file a bugzilla report if you can
get a reproducible case.
regards, tom lane
---(en
t?
> This has been brought up in the past. I don't think there's any reason
> there can't be one. Want to make a function appendix? :)
I think this is more conventionally called an index ;-)
regards, tom lane
---(end of broadcas
Bruce Momjian writes:
> !consistent between the various implementations. This chapter is also
> !not exhaustive; additional functions appear in relivant sections of
> !the manual.
"relevant", please.
regards, tom lane
---
ion that is in the individual reference pages today.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
olchain for that.
As far as I can tell, Red Hat is still depending on DocBook, so I think
that this format is not quite so dead as all that. Maybe we need to
take another look at exactly which tools we're using though ...
regards, tom lane
--
BAZ is interpreted as fooBARbaz, and "A weird"" name"
> becomes A weird" name.
Please observe the context in which that statement appears: it is
talking about backslash commands only.
For the syntax of SQL commands see
http://www.postgresql.org/docs/8.0/static
in the same way a SELECT does.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
maybe he forgot this
time? Or is there a more general problem with pgsql-committers? The
last traffic I got from it is
Subject: [COMMITTERS] pgsql: libpgport routines need nonstandard palloc to wor
which I committed just before leaving for the weekend on Saturday.
Was Alvaro's commit the o
I wrote:
> Was Alvaro's commit the only one over the weekend?
I pulled down the CVS logs and verified that it was the only such
commit. So the problem is most likely specific to Alvaro's account
and not a list-wide issue.
rega
curate about btree, but I'm not so sure about
GiST --- Teodor, any comments?
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
s of
whoever's making that scan.
(Memo to self: it's getting to be time for that again.)
regards, tom lane
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
languages first, but obviously it's not getting the job done.
Anybody have a better idea?
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
Bruce Momjian writes:
> Volkan YAZICI wrote:
>> Will PQregisterThreadLock() - which is defined globally in
>> src/interfaces/libpq/fe-connect.c - be documented?
> Yes, it should be documented.
Really? Do we intend applications to call it?
Bruce Momjian writes:
> Tom Lane wrote:
>> Really? Do we intend applications to call it?
> Uh, well, we never call it ourselves, so if we don't expect other
> applications to call it, why is it there?
If it's intended for apps to call, how was the patch initially accep
] Manfred Spraul
I note that PQinitSSL is likewise documentation-free.
Also, neither one of these two routines is listed in exports.txt,
meaning that Windows users are physically unable to call them
even if they knew they existed :-(
regards, tom lane
--
n additional columns restrict the
entries returned by the index, but the condition on the first column is the
most important one for determining how much of the index needs to be
scanned. A GiST index will be relatively ineffective if its first column
has only a few distinct values, ev
e will raise
Marc's hackles about whether we need another RC ;-)
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
n infinite loop ... I gave up waiting for it to redisplay after
trying to scroll down the bookmarks window. Even just displaying
successive pages is painfully slow.
I suspect there's something wrong with the toolset you're using.
regards, tom lane
x27;s on the static page.
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
ml. Can you send a patch to that file or should
> I merge your HTML into there?
What exactly is the point of the change at all?
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
CPU costs up.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Bruce Momjian writes:
> I suggest the following patch to rename our capability "Continuous
> Backup".
This doesn't seem like an improvement. "Online backup" is the standard
terminology AFAIK.
regards, tom lane
-
od.
That will just create more confusion down the road if we add another
feature that could also be called "continuous archiving".
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
are mostly empty would just
be clutter. Maybe create subdirectories only for modules that
have 'em in the source tree?
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your d
ain it, not necessary.
> is this acceptable or usefull? if so, i can do it after work...
It seems like clutter to me. Whether a catalog is shared or not is not
necessarily the first thing you want to know about it.
regards, tom lane
Bruce Momjian writes:
> Tom Lane wrote:
>> It seems like clutter to me. Whether a catalog is shared or not is not
>> necessarily the first thing you want to know about it.
> I am thinking the table should be split into two, one for the global
> tables, and another fo
od that material might be on its own.
Is it reasonable to try to make an outline of how you think the chapter
should go, or would that be premature without more discussion of
objectives?
regards, tom lane
---(end of broadcast)--
that part, and I'm not going to repay the
offer by asking him to redo the whole manual ;-)
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
p hearing is that the info is in there but it's
not so easy to find. So this sounds like a plan to me: quick overviews
with links should make it easier to find the parts people need to read.
regards, tom lane
---(end of broadcast)
t say that rather than emphasizing the "server
start time" aspect of it, which is exactly what not to emphasize.
Comments?
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
lso allow us to have a much longer description of all of the
> implications and difficulties of each mode.
We have all that in the introductory section; the references made in the
per-variable descriptions really have no impact on how verbose the
introductory text is ...
umbered page.
I've been annoyed before that we can't publish a stable URL for a given
release's notes until it's been superseded. CC'ing pgsql-docs to see
if anyone has an idea how to get the front release's notes into a
sub-page...
regards,
someone wants to step up and do the work to convert the existing
contrib doc files to sgml, I certainly won't stand in the way --- but
I'm not prepared to remove contrib entries just because they don't have
sgml-format docs.
regards, tom lane
---
belongs to an
existing process belonging to the postgres userid does Postgres believe
that the pidfile is valid.
It might be worth mentioning this as you suggest, but I think it's a
sufficiently low-probability case that your failure was probably due to
something else.
Someone (was it Scott Marlowe?) recently volunteered to draft a
complete restructuring of the admin docs --- so it would probably be
better to think about this as part of that effort rather than a
standalone change.
regards, tom lane
---(end of broadcast)---
d I agree it should go. The comment seems to have been
attached to both 7.4 and 8.1 at the same time --- it is useful for 7.4,
but not later versions.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0,
7;t avoid the problem of holding exclusive lock for a long
time.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
atches if applicable.
We could try this for awhile and see if it works.
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
me mtime (to within whatever the mtime granularity is, typ. 1 second).
The proposed rule should be OK as long as checkpoints (and ensuing
renames) can't occur oftener than the mtime granularity. If you're
checkpointing more than once a second, well, you need help ...
ularity of mtime (and assuming ls sorts by the real mtime not what
it shows you, but that's true everywhere AFAIK).
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
a WAL file, ie,
24 hex digits.
ls -t .../pg_xlog | grep
'^[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]$'
| head -1
that ls will sort on the basis of the truncated
mtime that it displays, which is not the actual behavior of ls AFAIK.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ch?
It seems to be a '>' condition not a '>=' condition, so it'd be
pretty awkward ... certainly not a one-liner.
I think everyone agrees that adding a SQL function would be a reasonable
thing to do, anyway.
regards, tom lane
-
only
reason for using tar format would be if you want to process the file
later with something other than pg_restore.
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
to; it's just one extra
step. But would it really be helpful on the documentation? I see where
.po works for a lot of short, independent error messages, but I don't
see it being real useful for big manuscripts.
regards, tom lane
---(
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I have a counter-question. What value is there in continuing to use
> SGML?
We're already used to it, and it's not clear what we'd buy from the
effort of converting all our documentation.
gt; No, we wouldn't do that.
Right, I can't imagine that we'd abandon support for pg_dump custom
format without many versions' warning. AFAIK we still read pg_dump
output from 7.0 if not earlier ...
regards, tom lane
---(end of broad
rse you can do that with a text editor on a plain
dump, if the dump's not too large for your editor to handle ...
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appro
e would probably be some small differences, but 99% of pg_restore's
output is just regurgitating SQL it finds in the dump file.
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please s
a lie.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
I think you need to split this into two questions. Only the last
para of what you have is actually relevant to the given question.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
urrent schema search path.
Whenever the pattern parameter is omitted completely, the \d commands display
all objects that are visible in the
current schema search path. To see all objects in the database, use the pattern
*.*.
regards, tom lane
-
7;m counting on my
fingers correctly, such a value would occupy 16 bytes natively, which
means that pushing it out-of-line would be a dead loss anyway. But he's
still not going to get more than 512 of them into an 8K page.
regards, tom lane
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Please let me know if there is anything else you would like me to do or add.
A round of copy-editing seems indicated, at least.
regards, tom lane
---(end of broadcast)
whereever SELECT is. I'm not at all sure what I'd do instead though.
Should we give VALUES its own reference page? That doesn't quite
seem helpful either. cc'ing to pgsql-docs for ideas.
regards, tom lane
---(end of broadcast)-
omething a client can issue directly. Every more-
complex case is apparently supposed to be handled by one-row-at-a-time
fetches from a cursor.
If you can persuade the community that they don't want SELECT in its
current form, you might be able to persuade me that VALUES shouldn't
be allo
101 - 200 of 948 matches
Mail list logo
