Thread: puzzled by the docs
The PostgreSQL Administrator's Guide which appears on the web http://www.postgresql.org/docs/admin/index.html is fairly different from the one which is packed with the 7.0.2 distribution. Which is the good one? I'm puzzled because the web version mentions the release 7.0.2 (the other one, doesn't). And the section 'Logging and Debuging' (in chap. 7 from the web version), mentions a 'postgres.conf' configuration file, some settings that are of interest for me (as 'LOG_PID' and 'LOG_TIMESTAMP').... but the distributed doc, instead, speaks of the 'pg_option' file, and doesn't mention those settings... Help! Am I missing something stupid? Hernan Gonzalez Buenos Aires, Argentina
Hernan Gonzalez <hgonzal@sinectis.com.ar> writes: > The PostgreSQL Administrator's Guide which appears on the web > http://www.postgresql.org/docs/admin/index.html > is fairly different from the one which is packed with > the 7.0.2 distribution. > Which is the good one? The files appearing under http://www.postgresql.org/docs/ are a snapshot of current development, not the docs that go with the most recent release. Any changes you see are work that will be in the next major release (ie, 7.1). We have been planning to rearrange the website so that the main docs page shows the most recent release, and the development snapshot appears someplace else, but I guess Vince hasn't got round to it yet ... regards, tom lane
On Tue, 27 Jun 2000, Tom Lane wrote: > Hernan Gonzalez <hgonzal@sinectis.com.ar> writes: > > The PostgreSQL Administrator's Guide which appears on the web > > http://www.postgresql.org/docs/admin/index.html > > is fairly different from the one which is packed with > > the 7.0.2 distribution. > > > Which is the good one? > > The files appearing under http://www.postgresql.org/docs/ are a > snapshot of current development, not the docs that go with the > most recent release. Any changes you see are work that will be > in the next major release (ie, 7.1). > > We have been planning to rearrange the website so that the main > docs page shows the most recent release, and the development > snapshot appears someplace else, but I guess Vince hasn't got > round to it yet ... > > regards, tom lane > http://www.Postgresql.org/users-lounge/index.html "Vince hasn't got round to it yet" 'cuze after the disk crash they weren't regenerated right away. I see now they have been but the URL was changed. That's now fixed. If I get "round to it" later I'll add a link from somewhere. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
Tom Lane wrote: > > Hernan Gonzalez <hgonzal@sinectis.com.ar> writes: > > The PostgreSQL Administrator's Guide which appears on the web > > http://www.postgresql.org/docs/admin/index.html > > is fairly different from the one which is packed with > > the 7.0.2 distribution. > > > Which is the good one? > > The files appearing under http://www.postgresql.org/docs/ are a > snapshot of current development, not the docs that go with the > most recent release. Any changes you see are work that will be > in the next major release (ie, 7.1). > > We have been planning to rearrange the website so that the main > docs page shows the most recent release, and the development > snapshot appears someplace else, but I guess Vince hasn't got > round to it yet ... > > regards, tom lane Ok. It would be nice, I think, if the docs specify (in the heading) to which version they correspond... Anyway, the 7.0.2 docs state (in the "pg_options" section) that : > Message printed to stdout or stderr are prefixed by a timestamp containing also the backend pid > > #timestamp #pid #message > 980127.17:52:14.173 [29271] StartTransactionCommand > 980127.17:52:14.174 [29271] ProcessUtility: dro > ... > This format improves readability of the logs and allows people to understand exactly which backend is > doing what and at which time. It also makes easier to write simple awk or perl scripts which monitor the > log to detect database errors or problem, or to compute transaction time statistics. It is very true that this format is useful, but that's not what I get. My 7.0.2 postmaster is started with stdout & stderr redirected to a file, and I get no timestamps no pids. My .../data/pg_options file contains two lines: verbose=1 query Am I doing something wrong ? Thanks! Hernan Gonzalez Buenos Aires, Argentina
I suggest you not worry too much about versions when using the
on-line docs. The doc's are ALWAYS for an earlier version. But they work
fine on a later version. Nothing much has changed from SQL92 which is 8
years old now.
If you learn to write good code with SQL92 it will run fine on
postgres AND other database.
On Tue, 27 Jun 2000, Hernan Gonzalez wrote:
> Tom Lane wrote:
> >
> > Hernan Gonzalez <hgonzal@sinectis.com.ar> writes:
> > > The PostgreSQL Administrator's Guide which appears on the web
> > > http://www.postgresql.org/docs/admin/index.html
> > > is fairly different from the one which is packed with
> > > the 7.0.2 distribution.
> >
> > > Which is the good one?
> >
> > The files appearing under http://www.postgresql.org/docs/ are a
> > snapshot of current development, not the docs that go with the
> > most recent release. Any changes you see are work that will be
> > in the next major release (ie, 7.1).
> >
> > We have been planning to rearrange the website so that the main
> > docs page shows the most recent release, and the development
> > snapshot appears someplace else, but I guess Vince hasn't got
> > round to it yet ...
> >
> > regards, tom lane
>
> Ok.
> It would be nice, I think, if the docs specify (in the heading)
> to which version they correspond...
>
> Anyway, the 7.0.2 docs state (in the "pg_options" section)
> that :
>
> > Message printed to stdout or stderr are prefixed by a timestamp containing also the backend pid
> >
> > #timestamp #pid #message
> > 980127.17:52:14.173 [29271] StartTransactionCommand
> > 980127.17:52:14.174 [29271] ProcessUtility: dro
> > ...
> > This format improves readability of the logs and allows people to understand exactly which backend is
> > doing what and at which time. It also makes easier to write simple awk or perl scripts which monitor the
> > log to detect database errors or problem, or to compute transaction time statistics.
>
> It is very true that this format is useful, but that's not what I get.
> My 7.0.2 postmaster is started with stdout & stderr redirected to a file,
> and I get no timestamps no pids.
>
> My .../data/pg_options file contains two lines:
>
> verbose=1
> query
>
> Am I doing something wrong ?
>
> Thanks!
>
> Hernan Gonzalez
> Buenos Aires, Argentina
>
>
Yours Truly,
- Karl F. Larsen, k5di@arrl.net (505) 524-3303 -
> > I suggest you not worry too much about versions when using the > on-line docs. The doc's are ALWAYS for an earlier version. But they work > fine on a later version. Nothing much has changed from SQL92 which is 8 > years old now. > > If you learn to write good code with SQL92 it will run fine on > postgres AND other database. Huh? The on-line docs cover more that just SQL. In particular the question being discussed had to do with log file formating. Also I don't know what is exactly in SQL92 but I don't think Postgres fully implements it yet. For example I presume that SQL92 includes outer joins, Postgres does not (yet). At some point it will. It would be a bad idea to assume that SQL92 complient code documented in say v8.0 would work on a 7.0 database.
Hernan Gonzalez wrote:
>Anyway, the 7.0.2 docs state (in the "pg_options" section)
>that :
>
>> Message printed to stdout or stderr are prefixed by a timestamp containi
>ng also the backend pid
>>
>> #timestamp #pid #message
>> 980127.17:52:14.173 [29271] StartTransactionCommand
>> 980127.17:52:14.174 [29271] ProcessUtility: dro
...
>It is very true that this format is useful, but that's not what I get.
>My 7.0.2 postmaster is started with stdout & stderr redirected to a file,
>and I get no timestamps no pids.
>
>My .../data/pg_options file contains two lines:
>
> verbose=1
> query
>
>Am I doing something wrong ?
It is a compilation option:
--- postgresql-7.0.2.orig/src/include/config.h.in
+++ postgresql-7.0.2/src/include/config.h.in
@@ -161,7 +161,8 @@
* ELOG_TIMESTAMPS: adds a timestamp with the following format to elog
* messages: yymmdd.hh:mm:ss.mmm [pid] message
*/
-/* #define ELOG_TIMESTAMPS */
+/* Turned on for Debian */
+#define ELOG_TIMESTAMPS
--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"For I am not ashamed of the gospel of Christ; for it
is the power of God unto salvation to every one that
believeth; to the Jew first, and also to the Greek."
Romans 1:16