The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/trigger-definition.html
Description:
https://www.postgresql.org/docs/devel/static/trigger-definition.html
This sentence:
"If an INSERT contains an ON CONFLICT DO UPDATE clause, i
SELECT some_field FROM data",
conn))
using (var reader = cmd.ExecuteReader())
while (reader.Read())
Console.WriteLine(reader.GetString(0));
}
For future reference Npgsql have wonderful documentation here
http://www.npgsql.org/index.html, and they prefer questions be poste
ons can also be declared to return
! a set, or table, or any data type they can return a
single
instance of. Such a function generates its output by executing
RETURN NEXT for each desired element of the result
set, or by using RETURN QUERY to output the result of
-N
On Wed, 2007-10-10 at 20:34 +0200, Guillaume Lelarge wrote:
> ... for revoke.sgml.
Applied, thanks.
-Neil
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/ab
On Tue, 2007-10-09 at 15:52 +0200, Guillaume Lelarge wrote:
> ... this time, for config.sgml.
Applied, thanks.
-Neil
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
h
Es from it during the
documentation build.
-Neil
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
ce, but not the sequence's name. While that argument doesn't apply
to ALTER VIEW at the moment, recent history suggests that it may only be
a matter of time before we need to add an ALTER VIEW command anyway...
(for instance, to control the properties of materialized or updateable
views).
-N
On Sat, 2007-30-06 at 00:26 -0400, Tom Lane wrote:
> There is exactly 0 chance of that happening, because it's always worked
> historically.
Agreed, but I think the patch should disallow ALTER VIEW ... RENAME on a
non-view, and ALTER SEQUENCE ... RENAME on a non-seque
AME forms change the name
of a table (or an index, sequence, or view) or the name of an individual
column in a table."
Of course, it could be made more obvious...
-Neil
---(end of broadcast)---
TIP 7: You can help support the PostgreS
On Tue, 2007-15-05 at 09:07 -0400, Alvaro Herrera wrote:
> I agree, the note should be added there (but it should be a short one
> and refer the reader someplace else for more complete details).
I've applied the attached patch to HEAD and REL8_2_STABLE.
-Neil
Index: doc/src/sgml/
change would be okay if we also removed one of the other mentions
in an unrelated section of the manual? I don't see the logic.
-Neil
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ror of the
CVS repository (which you can create via cvsup or rsync). With that
setup, "cvs add" and "cvs diff -N" work fine, since you can arrange for
write access to the local mirror.
(I'm always surprised to hear that anyone does a non-trivial amount of
work on Postgres wit
the
server should run the autovacuum launcher daemon" -- this is not
strictly true, and in any case, it isn't the whole story.
> The proposed addition to postgresql.conf seems particularly
> over-the-top
I agree that this information doesn't really b
On Thu, 2007-26-04 at 18:07 -0400, Neil Conway wrote:
> (1) I believe the reasoning for Tom's earlier change was not to reduce
> the I/O between the backend and the pgstat process [...]
Tom, any comments on this? Your change introduced an undocumented
regression into 8.2. I think yo
On Thu, 2007-03-05 at 15:32 +0100, Brian Gough wrote:
> Here is a patch for some doubled words in the manual
> (e.g. "the the").
Applied, thanks for the patch.
-Neil
---(end of broadcast)---
TIP 1: if posting/reading through Use
instead?
-Neil
Index: doc/src/sgml/monitoring.sgml
===
RCS file: /home/neilc/postgres/cvs_root/pgsql/doc/src/sgml/monitoring.sgml,v
retrieving revision 1.49
diff -c -p -r1.49 monitoring.sgml
*** doc/src/sgml/monitoring.sgml 26 Apr 2007 22
On Tue, 2007-04-24 at 17:38 -0400, Neil Conway wrote:
> which included other modifications to reduce the pgstat I/O volume in
> 8.1. I don't think this particular change was wise
I looked into this a bit further:
(1) I believe the reasoning for Tom's earlier change was not t
/O volume in
8.1. I don't think this particular change was wise: the reduction in
pgstat volume is pretty marginal, and it is counter-intuitive for
stats_row_level to effect whether the last ANALYZE / VACUUM is recorded.
(Plus, the optimization is not even enabled with the default
postgresq
t last
> vacuum/analyze execution time.
Why is this so? It sounds more like a bug than a feature to me.
-Neil
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
On Tue, 2007-04-10 at 17:24 +0200, Peter Eisentraut wrote:
> The new uuid type is lacking documentation.
We had also talked about including some UUID generation functionality in
8.3, but it should be okay to leave that for 8.4.
-Neil
---(end of broadc
> Just a suggestion. If this strikes others as a good idea, I'd be happy
> to draft something.
Makes sense to me. Would you mind submitting a patch against the SGML
docs?
-Neil
---(end of broadcast)---
TIP 1: if posting/reading th
nice to ensure
that linked versions of same are typeset in a similar manner.
If you'd like to improve the cross-referencing, please go ahead and
submit patches.
-Neil
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
rsonally I don't think that's an improvement, although I'm not
completely satisfied with "Server Configuration" either.
> But then why isn't that under Managing Databases :)
Because that chapter describes managing individual databases and
tablespaces, not an entir
ing what causes the difference, what the performance
impact is likely to be, or how to workaround the problem isn't likely to
be very helpful.
-Neil
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
onal improvements, so once it's in CVS
anyone else who's interested can have at it.
-Neil
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ithin 24 hours.
-Neil
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
hapters called
>
> Server Run-time Environment
> Run-time Configuration
>
> to be
>
> Server and Operating System Environment
> Server Configuration Parameters
IMHO "Operating System Environment" and "Server Configuration" would be
more conci
S
> + SELECT * FROM country WHERE country_name LIKE 'A%';
> + COPY a_list_countries TO '/usr1/proj/bray/sql/a_list_countries.copy';
> + ROLLBACK;
> +
> +
The capitalization of "a_list_countries" is inconsistent -- both
references should all
database is in danger of xid wraparound and
! VACUUMs the whole database if needed.
AFAIK contrib/pg_autovacuum in 8.0 also checked for XID wraparound (or
at least its documentation claims that it does), so I don't see how this
is new functionality.
m variables:
! custom_variable_classes = 'plperl,plr,pljava'
plr.path = '/usr/lib/R'
pljava.foo = 1
+ plperl.use_strict = true # now without having to use pl/perlU! :)
plruby.bar = true# generates error, unknown class name
I didn't see why this was relevant, so I didn't apply it.
-Neil
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
tions, using gmake.
You can get the prebuilt PDFs from:
http://www.postgresql.org/docs/manuals/
If you need to build them yourself, be prepared for it to take quite
some time...
-Neil
---(end of broadcast)---
TIP 6: Have you searched our
Neil Conway wrote:
The function definition tables in func.sgml use punctuation
inconsistently: some descriptions are terminated by a period, some are
not. Is there any opinion on which variant is "correct"?
I ended up not including a period in single-sentence function
descriptions,
; is the correct variant, but I don't have an authoritative
reference. AFAIK there is no grammatical difference, anyway.
-Neil
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
e" as well,
and specifies that "table" really means "table or view". Similarly, the
INSERT syntax summary talks about "INSERT INTO table ...", although of
course you can insert into a view if the appropriate rule exists. A view
is a table in more ways than one
David Fetter wrote:
Please find enclosed a patch which adds cross-references to the CREATE
FUNCTION syntax in the PL/* docs.
I thought the PL/PgSQL hunk wasn't an appropriate place for an ,
so I didn't apply that. The rest of the patch was applied with minor
edits -- thanks for the pat
ds, rather than terminated: so single sentence
descriptions will have no period, and multiple sentence descriptions
will have periods except for the last sentence. I have a vague
recollection that we use this style elsewhere...
-Neil
---(end of broadcast)--
, thanks.
-Neil
---(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
owing patch to head; it makes
the first reference to "INSERT" in that page an xref, as well as making
a few other minor improvements.
I notice most commands are not done this way.
Yeah, there's not much point linking each and every reference to a SQL
command.
-Neil
Index: d
Hashem Masoud wrote:
This patch corrects typos in xfunc.sgml [...]
Thanks; typos fixed in HEAD and REL8_0_STABLE.
-Neil
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Wed, 2005-02-09 at 15:38 +0100, Rainer Brandt wrote:
> a suggestion for a small improvement in the 8.0 manual:
>
> The term 'raise' (see section 35.9) is not in the index.
Thanks for the suggestion; I've applied the attached patch to CVS HEAD.
-Neil
Index: d
or specific improvements are welcome (a patch against the
SGML is easiest).
-Neil
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
e Environment" chapter, but I don't think that's the
first place most people would look. What do people think about
separating the configuration section out to be a new top-level chapter?
-Neil
---(end of broadcast)---
TIP 5: Have y
e. If I have done that incorrectly, please let me know.
-Neil
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
reference pages to refer to
SQL:2003 consistently. At present they refer to a mix of SQL-92,
SQL:1999, and SQL:2003.
-Neil
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Thu, 2004-09-30 at 13:58, Alvaro Herrera wrote:
> Cool! Please apply this one as well ;-)
Patch applied, with some editorializing. Thanks!
-Neil
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan
On Wed, 2004-09-29 at 23:21, Kris Jurka wrote:
> This adds an index entry for tablespaces which is tricky to find
> otherwise.
Patch applied -- thanks!
(FWIW, adding index entries for stuff is a pretty easy TODO item, if
anyone's looking for something worth contributing
On Sat, 2004-09-11 at 02:41, Thomas F.O'Connell wrote:
> Well, here's a patch for select.sgml should a committer ever feel
> inspired:
Patch applied -- thanks.
-Neil
---(end of broadcast)---
TIP 6: Have you searched o
ike PS and PDF). So that's been another reason we haven't bothered with
this in the past. I tend to agree with Tom that it's not really worth
the trouble to backport these kinds of fixes, as long as it's just a
cosmetic typo.
-Neil
--
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in the 7.4.x
docs:
Since it's fixed in HEAD, I think we're fine -- we usually don't bother
applying documentation fixes to release branches, even if there were
plans for
vantage of the hypertext
nature of HTML (and PDF, although I'm not sure if the PDF versions of
our docs support links -- in theory they could...)
Unless anyone objects, I'll start making the necessary changes soon.
An example of the kind of change I'm planning is attac
es something from $PGDATA without understanding what
it is, they deserve what they get.
I do agree that we could stand to document the purpose of pg_clog
and pg_xlog more clearly. However, this information belongs in the
standard documentation, not scattered throughout $PGDATA.
-Neil
-
51 matches
Mail list logo
