The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/sql-prepare-transaction.html
Description:
Hi, in prepare transaction documentation in PG10 and earlier, it says that
you can't prepare a transaction with LISTEN or UNLISTEN but it d
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/queries-with.html
Description:
Searching for the word "with" in the documentation, returns no
results. This
is strange when there are pages titled "WITH queries".
I presume the w
XTRACT(CENTURY FROM TIMESTAMP '2100-02-16 20:38:40');
Result: 21
If I have missed some point about how this should work, then please ignore this
e-mail.
Thanks,
Mark Clark
mark.cl...@enlightedinc.com
I'm sending the patch below for inclusion.
Originally I ran this by pgsql-hackers, just to confirm the docs (and not
the code) were in need of the fix, which seems to be the case:
http://archives.postgresql.org/pgsql-hackers/2011-09/msg00614.php
Thanks
--
Mark
-- Forwarded me
Hi am I looking at the 9.0/9.1 release docs.
(http://developer.postgresql.org/pgdocs/postgres/release-9-0.html)
E.1.3.2. Queries
the 4th bullet point says
"Have SELECT and CREATE TABLE AS return row counts to the client
(Boszormenyi Zoltan)
For drivers that support this feature, this saves
The above is not as robust as the original, since it doesn't retry, and it's
a bit of a foot-gun if you don't actually have a unique constraint... Maybe
someone else can come up with a version that's strictly better than the old
one, and still plays nice with suppress_redundant_updates.
Thanks!
Mark
Simon Riggs wrote:
On Wed, 2008-11-26 at 22:14 +1300, Mark Kirkwood wrote:
Exactly, after posting this I discovered the relevant CVS logs for
changes to support restartable recovery. It seems to me that perhaps a
little more detail in the docs would be good here.
I would hope that
Simon Riggs wrote:
On Fri, 2008-08-22 at 00:50 -0500, Decibel! wrote:
On Aug 13, 2008, at 4:59 AM, Mark Kirkwood wrote:
I noticed in the docs for pg_standby (docs/src/sgml/pgstandby.sgml)
that we have supported version >= 8.2. However it does seem to work
ok with earlier versi
I noticed in the docs for pg_standby (docs/src/sgml/pgstandby.sgml) that
we have supported version >= 8.2. However it does seem to work ok with
earlier versions (e.g 8.1) - or am I missing something?
cheers
Mark
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make chan
Alvaro Herrera wrote:
Mark Kirkwood wrote:
Alvaro Herrera wrote:
Except that it also includes diffs for generated files, which tend to be
huge. To work around that you need to create a list of files to
exclude, and the whole thing (which was cumbersome already) starts to
get unmanageable
Alvaro Herrera wrote:
David Fetter wrote:
On Mon, May 14, 2007 at 03:31:40PM +1200, Mark Kirkwood wrote:
David Fetter wrote:
cvs diff works just great until you want to add or remove a file
without write permissions to the CVS repository, i.e. when you've
checked out as anonymous.
I us
-Nacr pgsql.orig pgsql
gives a complete patch including added/deleted files. It is a bit
primitive, but is pretty easy to do!
Cheers
Mark
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-n
Bruce Momjian wrote:
> Mark Stosberg wrote:
>> It woud also be nice to document that the full names "custom" and "tar" are
>> supported. Longer names can be nice for clarity.
>>
>> ( Unfortunately, wrong formats like "txx" also work inst
Peter Eisentraut wrote:
> Am Freitag, 9. März 2007 03:30 schrieb Mark Stosberg:
>> The tar format needs some space to create temporary files. By default
>> "/tmp" is used. On systems with small "/tmp" partitions, set the
>> "TMPDIR" environm
"custom" and "tar" are
supported. Longer names can be nice for clarity.
( Unfortunately, wrong formats like "txx" also work instead of throwing
an error. )
Mark
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
ult - even as a complete SGML newbie - to get up and running, make
my changes and build the (HTML) docs.
Cheers
Mark
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Theo Kramer wrote:
On the ODBC types - I found these useful as my interface is based on
that. I imagine that others who have used ODBC and who would like to use
the libpq functions may also find it useful, but also agree that it may
be misleading.
Perhaps, with a couple of iterations, we can g
Mark Kirkwood wrote:
Peter Eisentraut wrote:
Mark Kirkwood wrote:
$ make man
...
onsgmls postgres.sgml | sgmlspl
/usr/share/sgml/docbook/utils-0.6.14/helpers/docbook2man-spec.pl
--lowercase --section l --date "`date '+%Y-%m-%d'`"
Unknown SDATA: [mdash ] at
/usr/share/sgml/
Peter Eisentraut wrote:
Mark Kirkwood wrote:
$ make man
...
onsgmls postgres.sgml | sgmlspl
/usr/share/sgml/docbook/utils-0.6.14/helpers/docbook2man-spec.pl
--lowercase --section l --date "`date '+%Y-%m-%d'`"
Unknown SDATA: [mdash ] at
/usr/share/sgml/docbook/utils-0.6.14
2man-spec.pl at a certain
stylesheet? Any ideas appreciated.
Cheers
Mark
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On 2006-05-03, Tom Lane <[EMAIL PROTECTED]> wrote:
> Mark Stosberg <[EMAIL PROTECTED]> writes:
>> A suggested addition to the pg_dump docs:
>> This would be an extension to the documentation for the "tar" format:
>
>> The tar format needs some space
"custom" and "tar" are
supported. Longer names can be nice for clarity.
( Unfortunately, wrong formats like "txx" also work instead of throwing
an error. )
Mark
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Robert Treat wrote:
I thought it was more correct to use < rather than < inside of
tags?
I am unsure about this myself (I copied the usage from perform.sgml).
Mark
---(end of broadcast)---
TIP 2: you can get off all lists at once wi
Bruce Momjian wrote:
Mark Kirkwood wrote:
At Tom's suggestion, I am going to amend the page to fit into the
'internals' chapter as opposed to 'performance tips' one. I might do
this first, and send you the resulting page.
That sounds good, that this become part of the
will do the edit).
How does that sound?
At Tom's suggestion, I am going to amend the page to fit into the
'internals' chapter as opposed to 'performance tips' one. I might do
this first, and send you the resulting page.
regards
Mark
---
Josh Berkus wrote:
Mark,
Terrific. I'd be happy to post this at www.powerpostgresql.org, if you want;
I think a lot of people would be interested.
Absolutely, that is an excellent spot for it, do you need it reformatted
in html first?
BTW - in fact a community site may well be
Post feedback changes - thanks to all who commented!
Mark Kirkwood wrote:
I wanted to understand how the planner 'knows' how many rows are likely
to be emitted in a given stage of a query, and wrote down some examples
for my own benefit - I then wondered if this would be a good addit
mments welcome.
best wishes
Mark
--- perform.sgml.orig Sat Feb 5 12:45:36 2005
+++ perform.sgmlTue Feb 8 15:08:02 2005
@@ -470,6 +470,288 @@
+
+
+ How the Planner Uses Statistics
+
+
+ statistics
+ of the planner
+
+
+
+ This section builds on the material covered in
Attached are my first thoughts for the amended instructions.
Mark Kirkwood wrote:
But to be on the safe side, it would make sense to do something similar
to the BSD section, and comment about older distributions maybe needing
to manipulate /proc/kernel/* directly.
--- runtime.sgml.orig Fri Feb
Tom Lane wrote:
Mark Kirkwood <[EMAIL PROTECTED]> writes:
Glancing over these as I was doing the FreeBSD patch, I noticed some
scope for modernization there plus a possible error to correct:
i) we could standardize the change method to use sysctl instead of
echo'ing things into /
option is to follow what we have said for the BSD's i.e:
kernel.shmall = 32768
or leave shmall at its default (commonly 2097152).
What do people think?
regards
Mark
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
, not after, so maybe that should be "see below".
Thanks - had not considered that!
Amended patch attached.
regards
Mark
--- runtime.sgml.orig Sat Jan 29 18:30:50 2005
+++ runtime.sgmlTue Feb 1 14:25:53 2005
@@ -4351,9 +4351,51 @@
FreeBSD
+ FreeBSDIPC
NetBSD are in need of an update too,
however I don't have any installations of such to experiment on.
regards
Mark
--- runtime.sgml.orig Sat Jan 29 18:30:50 2005
+++ runtime.sgmlMon Jan 31 22:30:35 2005
@@ -4350,10 +4350,8 @@
- FreeBSD
NetBSD
Op
Hmmm ... good point - configure thinks I am running 4.2, but the
stylesheets etc might be more recent than postgresql.org's:
$ rpm -qa|grep docbook
docbook-dtds-1.0-25
docbook-style-dsssl-1.78-4
Tom Lane wrote:
Mark Kirkwood <[EMAIL PROTECTED]> writes:
I am seeing a docs bu
f that was the intent of the previous change tho)
regards
Mark
---(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
I believe the ODBC driver works this way by design. So it's just something you
need to know if you plan to use it with updateable cursors.
It is my impression that the Postgres ODBC driver is somewhat of a "poor
stepchild" within the Postgres community. However, it appears
Title: Re: disabling OIDs?
For what it's worth, OIDs are required if you ever want to use updateable cursors with the ODBC driver. We discovered this the hard way. Mark Dexter
ON
e.bonus_plan = bp.planid
WHERE employees.employeeid = e.employeeid
Thanks. Mark Dexter
Here's a note on using the async API. It's not runnable code (due to
the variances in event loop packages), but I'm happy to add this
to whatever documentation package is appropriate...
Advice and feedback welcomed...
Mark
Application Note: Integrating Posgresql queries into an e
39 matches
Mail list logo
