pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedError in documentation
8+ messages / 6 participants
[nested] [flat]
* Error in documentation
@ 2001-05-02 11:34 Justin Clift <jclift@iprimus.com.au>
0 siblings, 1 reply; 8+ messages in thread
From: Justin Clift @ 2001-05-02 11:34 UTC (permalink / raw)
To: pgsql-docs
Hi guys,
Just noticed an error in the 7.1.1 developer docs.
In the Admin Guide, in chapter 3.3 "Starting the database server" it
says :
***
On Solaris, edit the file rc2.d to contain the following single line:
su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D
/usr/local/pgsql/data"
***
This is BADLY WRONG and won't work at all.
Instead the person installing PostgreSQL needs to create a startup
script as /etc/init.d/postgresql, then create a soft link from
/etc/rc3.d/S[00..99]postgresql that script.
The script though, can use the su command given above.
i.e.
echo 'su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D
/usr/local/pgsql/data"' > /etc/init.d/postgresql
chmod 744 /etc/init.d/postgresql
chown root:sys /etc/init.d/postgresql
ln -s /etc/init.d/postgresql /etc/rc3.d/S10postgresql
I haven't tried looking at the documentation .sgml source files and
creating a patch, but if you guys want me to, I guess I could figure it
out.
Regards and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Error in documentation
@ 2001-05-07 15:55 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Justin Clift <jclift@iprimus.com.au>
0 siblings, 1 reply; 8+ messages in thread
From: Bruce Momjian @ 2001-05-07 15:55 UTC (permalink / raw)
To: Justin Clift <jclift@iprimus.com.au>; +Cc: pgsql-docs
OK, I have applied the following patch to clean up the Solaris problems
you reported.
> Hi guys,
>
> Just noticed an error in the 7.1.1 developer docs.
>
> In the Admin Guide, in chapter 3.3 "Starting the database server" it
> says :
>
> ***
>
> On Solaris, edit the file rc2.d to contain the following single line:
>
> su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D
> /usr/local/pgsql/data"
>
> ***
>
> This is BADLY WRONG and won't work at all.
>
> Instead the person installing PostgreSQL needs to create a startup
> script as /etc/init.d/postgresql, then create a soft link from
> /etc/rc3.d/S[00..99]postgresql that script.
>
> The script though, can use the su command given above.
>
> i.e.
>
> echo 'su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D
> /usr/local/pgsql/data"' > /etc/init.d/postgresql
> chmod 744 /etc/init.d/postgresql
> chown root:sys /etc/init.d/postgresql
> ln -s /etc/init.d/postgresql /etc/rc3.d/S10postgresql
>
> I haven't tried looking at the documentation .sgml source files and
> creating a patch, but if you guys want me to, I guess I could figure it
> out.
>
> Regards and best wishes,
>
> Justin Clift
>
> --
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
> - Indira Gandhi
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Attachments:
/bjm/diff (text/plain, 1.2K) download
Index: doc/src/sgml/runtime.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/runtime.sgml,v
retrieving revision 1.63
diff -c -r1.63 runtime.sgml
*** doc/src/sgml/runtime.sgml 2001/05/04 23:11:37 1.63
--- doc/src/sgml/runtime.sgml 2001/05/07 15:53:22
***************
*** 254,264 ****
<listitem>
<para>
! On <productname>Solaris</productname>, edit the file
! <filename>rc2.d</filename> to contain the following single line:
<programlisting>
su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data"
</programlisting>
</para>
</listitem>
</itemizedlist>
--- 254,267 ----
<listitem>
<para>
! On <productname>Solaris</productname>, create a file called
! <filename>/etc/init.d/postgresql</filename> to contain the following
! single line:
<programlisting>
su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data"
</programlisting>
+ Then, create a symlink to it in <filename>/etc/rc3.d</> as
+ <literal>S99postgresql</>.
</para>
</listitem>
</itemizedlist>
* Re: Error in documentation
@ 2001-05-07 22:31 Justin Clift <justin@postgresql.org>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 8+ messages in thread
From: Justin Clift @ 2001-05-07 22:31 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: Justin Clift <jclift@iprimus.com.au>; pgsql-docs
Hi Bruce,
Yep, that should work fine. :-)
Regards and best wishes,
Justin Clift
Bruce Momjian wrote:
>
> OK, I have applied the following patch to clean up the Solaris problems
> you reported.
>
> > Hi guys,
> >
> > Just noticed an error in the 7.1.1 developer docs.
> >
> > In the Admin Guide, in chapter 3.3 "Starting the database server" it
> > says :
> >
> > ***
> >
> > On Solaris, edit the file rc2.d to contain the following single line:
> >
> > su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D
> > /usr/local/pgsql/data"
> >
> > ***
> >
> > This is BADLY WRONG and won't work at all.
> >
> > Instead the person installing PostgreSQL needs to create a startup
> > script as /etc/init.d/postgresql, then create a soft link from
> > /etc/rc3.d/S[00..99]postgresql that script.
> >
> > The script though, can use the su command given above.
> >
> > i.e.
> >
> > echo 'su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D
> > /usr/local/pgsql/data"' > /etc/init.d/postgresql
> > chmod 744 /etc/init.d/postgresql
> > chown root:sys /etc/init.d/postgresql
> > ln -s /etc/init.d/postgresql /etc/rc3.d/S10postgresql
> >
> > I haven't tried looking at the documentation .sgml source files and
> > creating a patch, but if you guys want me to, I guess I could figure it
> > out.
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> > --
> > "My grandfather once told me that there are two kinds of people: those
> > who work and those who take the credit. He told me to try to be in the
> > first group; there was less competition there."
> > - Indira Gandhi
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
> >
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ------------------------------------------------------------------------
> Index: doc/src/sgml/runtime.sgml
> ===================================================================
> RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/runtime.sgml,v
> retrieving revision 1.63
> diff -c -r1.63 runtime.sgml
> *** doc/src/sgml/runtime.sgml 2001/05/04 23:11:37 1.63
> --- doc/src/sgml/runtime.sgml 2001/05/07 15:53:22
> ***************
> *** 254,264 ****
>
> <listitem>
> <para>
> ! On <productname>Solaris</productname>, edit the file
> ! <filename>rc2.d</filename> to contain the following single line:
> <programlisting>
> su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data"
> </programlisting>
> </para>
> </listitem>
> </itemizedlist>
> --- 254,267 ----
>
> <listitem>
> <para>
> ! On <productname>Solaris</productname>, create a file called
> ! <filename>/etc/init.d/postgresql</filename> to contain the following
> ! single line:
> <programlisting>
> su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data"
> </programlisting>
> + Then, create a symlink to it in <filename>/etc/rc3.d</> as
> + <literal>S99postgresql</>.
> </para>
> </listitem>
> </itemizedlist>
>
> ------------------------------------------------------------------------
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
^ permalink raw reply [nested|flat] 8+ messages in thread
* Error in documentation
@ 2002-03-01 20:20 andreas moroder <amoroder@sb-brixen.it>
0 siblings, 1 reply; 8+ messages in thread
From: amoroder@sb-brixen.it @ 2002-03-01 20:20 UTC (permalink / raw)
To: pgsql-docs
Hello,
in the tutorial ( HTML and PDF ) I found the folowing example
The new declaration of the tables would look like this:
CREATE TABLE cities (
name varchar(80) primary key,
location point
);
Chapter 3. Advanced Features
CREATE TABLE weather (
city varchar(80) references weather,
temp_lo int,
temp_hi int,
prcp real,
date date
);
Is this ok should the reference not be "references cities" ?
Bye
Andreas
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Error in documentation
@ 2002-03-07 17:52 Bruce Momjian <pgman@candle.pha.pa.us>
parent: andreas moroder <amoroder@sb-brixen.it>
0 siblings, 0 replies; 8+ messages in thread
From: Bruce Momjian @ 2002-03-07 17:52 UTC (permalink / raw)
To: andreas moroder <amoroder@sb-brixen.it>; +Cc: pgsql-docs
Yes, I we already fixed this. Don't remember if the fix is in 7.2.
In fact, I see this:
revision 1.27
date: 2002/02/12 22:25:15; author: momjian; state: Exp; lines: +3 -3
Fix tutorial for references problem, from rainer.tammer@spg.schulergroup.com
which means it didn't make it into 7.2. It should be OK in the online
docs, and in 7.3.
---------------------------------------------------------------------------
andreas moroder wrote:
> Hello,
>
> in the tutorial ( HTML and PDF ) I found the folowing example
>
> The new declaration of the tables would look like this:
> CREATE TABLE cities (
> name varchar(80) primary key,
> location point
> );
>
> Chapter 3. Advanced Features
>
> CREATE TABLE weather (
> city varchar(80) references weather,
> temp_lo int,
> temp_hi int,
> prcp real,
> date date
> );
>
> Is this ok should the reference not be "references cities" ?
>
> Bye
> Andreas
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 8+ messages in thread
* error in documentation?
@ 2007-09-24 14:03 Michael Cochez <michaelcochez@yahoo.com>
0 siblings, 1 reply; 8+ messages in thread
From: Michael Cochez @ 2007-09-24 14:03 UTC (permalink / raw)
To: pgsql-docs
In http://www.postgresql.org/docs/8.2/static/tutorial-transactions.html
"After rolling back to a savepoint, it continues to be defined, so you can roll back to it several times. Conversely, if you are sure you won't need to roll back to a particular savepoint again, it can be released, so the system can free some resources. Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it."
mustn't it be :
"After rolling back to a savepoint, it continues to be defined, so you can roll back to it several times. Conversely, if you are sure you won't need to roll back to a particular savepoint again, it can be released, so the system can free some resources. Keep in mind that rolling back to a savepoint will automatically release all savepoints that were defined after it and releasing a savepoint will automatically release all savepoints defined before it."
if not, could you please explain why this decision is made?
thanks,
Michael
---------------------------------
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: error in documentation?
@ 2007-09-24 14:15 Phil Frost <phil@macprofessionals.com>
parent: Michael Cochez <michaelcochez@yahoo.com>
0 siblings, 1 reply; 8+ messages in thread
From: Phil Frost @ 2007-09-24 14:15 UTC (permalink / raw)
To: Michael Cochez <michaelcochez@yahoo.com>; +Cc: pgsql-docs
On Sep 24, 2007, at 10:03 , Michael Cochez wrote:
> In http://www.postgresql.org/docs/8.2/static/tutorial-
> transactions.html
> "After rolling back to a savepoint, it continues to be defined, so
> you can roll back to it several times. Conversely, if you are sure
> you won't need to roll back to a particular savepoint again, it can
> be released, so the system can free some resources. Keep in mind
> that either releasing or rolling back to a savepoint will
> automatically release all savepoints that were defined after it."
> mustn't it be :
> "After rolling back to a savepoint, it continues to be defined, so
> you can roll back to it several times. Conversely, if you are sure
> you won't need to roll back to a particular savepoint again, it can
> be released, so the system can free some resources. Keep in mind
> that rolling back to a savepoint will automatically release all
> savepoints that were defined after it and releasing a savepoint
> will automatically release all savepoints defined before it."
>
> if not, could you please explain why this decision is made?
> thanks,
> Michael
If I do:
savepoint one;
update foo set bar = 2;
savepoint two;
update baz set foo = 3;
savepoint three;
delete from foo;
Why would it make sense to release "one" if i release "two"? If I
release "two", then it makes sense that I can never go back to "two"
or "three", but your proposed change means that if I release "two", I
can later rollback to "three" but not to "one". I don't see how
that's useful.
Essentially what the docs say is that savepoints are created on a
stack, and when you do something to to a savepoint "s", you
implicitly do the same thing to all the other savepoints above "s".
Or, if you think of them being nested:
savepoint one {
update foo set bar = 2;
savepoint two {
update baz set foo = 3;
savepoint three {
delete from foo;
...
}
...
}
...
}
then any operation on a savepoint also applies to any savepoints
nested within it.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: error in documentation?
@ 2007-09-24 16:34 Michael Cochez <michaelcochez@yahoo.com>
parent: Phil Frost <phil@macprofessionals.com>
0 siblings, 0 replies; 8+ messages in thread
From: Michael Cochez @ 2007-09-24 16:34 UTC (permalink / raw)
To: pgsql-docs
My reasoning was :
Look to every query on a time line
savepoint 1
query 1
....
savepoint j
query j
.....
savepoint n
query n
When I release savepoint j , I think 'everythin before savepoint j is ok and safe', and so I don't need the savepoints before savepoint j anymore (cause they're save) when I do a rollback to savepoint j, I say 'everything done after savepoint j is rubbish' so I don't need the savepoints after j anymore
Lets say I release savepoint j, why wouldn't it make sense to go back to savepoint j+1, (a state after the state beeing released).
I tought of releasing a savepoint as 'everything up to that savepoint is ok, I'm not yet shure about the queries coming next'
Michael
Phil Frost <phil@macprofessionals.com> wrote:
If I do:
savepoint one;
update foo set bar = 2;
savepoint two;
update baz set foo = 3;
savepoint three;
delete from foo;
Why would it make sense to release "one" if i release "two"? If I
release "two", then it makes sense that I can never go back to "two"
or "three", but your proposed change means that if I release "two", I
can later rollback to "three" but not to "one". I don't see how
that's useful.
Essentially what the docs say is that savepoints are created on a
stack, and when you do something to to a savepoint "s", you
implicitly do the same thing to all the other savepoints above "s".
Or, if you think of them being nested:
savepoint one {
update foo set bar = 2;
savepoint two {
update baz set foo = 3;
savepoint three {
delete from foo;
...
}
...
}
...
}
then any operation on a savepoint also applies to any savepoints
nested within it.
---------------------------------
Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more!
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2007-09-24 16:34 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-05-02 11:34 Error in documentation Justin Clift <jclift@iprimus.com.au>
2001-05-07 15:55 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-05-07 22:31 ` Justin Clift <justin@postgresql.org>
2002-03-01 20:20 Error in documentation andreas moroder <amoroder@sb-brixen.it>
2002-03-07 17:52 ` Bruce Momjian <pgman@candle.pha.pa.us>
2007-09-24 14:03 error in documentation? Michael Cochez <michaelcochez@yahoo.com>
2007-09-24 14:15 ` Re: error in documentation? Phil Frost <phil@macprofessionals.com>
2007-09-24 16:34 ` Re: error in documentation? Michael Cochez <michaelcochez@yahoo.com>
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