Hi doc keepers,
while I was looking for which privilege is to be granted to a user so the
user can lock tables, I found that information missing in the manual.
Therefore I tried to add it to the sgml doc sources:
postgresql-7.4.6/doc/src/sgml/ref/grant.sgml
134c134,135
Ralph Graulich wrote:
> while I was looking for which privilege is to be granted to a user so
> the user can lock tables, I found that information missing in the
> manual.
It's on the reference page of LOCK, where it belongs.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Hi Peter,
It's on the reference page of LOCK, where it belongs.
That's where I finally found it. Comparing the notes on different SQL
commands and the reference page for GRANT, I still consider it's worth
mentioning it there, as it is not that obvious like SELECT, INSERT or
DELETE privileges.
T
On Mon, Jan 31, 2005 at 09:16:11PM +0100, Peter Eisentraut wrote:
> Ralph Graulich wrote:
> > while I was looking for which privilege is to be granted to a user so
> > the user can lock tables, I found that information missing in the
> > manual.
>
> It's on the reference page of LOCK, where it bel
Alvaro Herrera wrote:
> It's useful (and consistent) to have a mention on the GRANT page.
> Else, the list in GRANT should be a plain list of available
> privileges, without the text that currently follows each.
In any case, his proposed change was wrong because the required
privileges depend on
Ralph Graulich <[EMAIL PROTECTED]> writes:
> The way the question occured while creating a user allowed to pg_dump
> certain databases, but not allowed to do anything else. That way I only
> granted SELECT privileges on the tables to that user, but that didn't
> work, as pg_dump wants to lock th
A recent mailing on the -perf list highlighted that the docs concerning
ipc configuration are a bit out for date for FreeBSD.
The attached patch separates out FreeBSD from Open/NetBSD, and shows how
to change settings via sysctl w/o a kernel rebuild. Any thoughts?
BTW I suspect that both Open and N
Mark Kirkwood <[EMAIL PROTECTED]> writes:
> A recent mailing on the -perf list highlighted that the docs concerning
> ipc configuration are a bit out for date for FreeBSD.
> The attached patch separates out FreeBSD from Open/NetBSD, and shows how
> to change settings via sysctl w/o a kernel rebuild
Tom Lane wrote:
This seems a bit awkwardly phrased:
+
+Versions before 4.0 will require a kernel rebuild, see the
+NetBSD and
+class="osname">OpenBSD instructions above, however the key word is
+options (plural) in this case.
Perhaps
FreeB
Hi everyone,
I don't know if this is the right place for this, but
the documentation of Postgresql 8.1Devel has a
statement
in the section "12.2. Transaction Isolation" that is
lacking "that":
Since the cost of redoing complex transactions may be
significant, this mode is recommended only when
u
Hashem Masoud <[EMAIL PROTECTED]> writes:
> I don't know if this is the right place for this, but
> the documentation of Postgresql 8.1Devel has a
> statement
> in the section "12.2. Transaction Isolation" that is
> lacking "that":
> Since the cost of redoing complex transactions may be
> signific
The numbering in the FAQ table of contents doesn't always agree
with the numbering in the body. For example, the table of contents
has this:
4.11.0) How do I create a serial/auto-incrementing field?
4.11.1) How do I get the value of a SERIAL insert?
4.11.2) Doesn't currval() lead to a race condit
12 matches
Mail list logo
