pg_language;
pg_language
-
(internal,10,f,f,0,0,2246,)
(c,10,f,f,0,0,2247,)
(sql,10,f,t,0,0,2248,)
(plpgsql,10,t,t,12319,12320,12321,)
Any idea where this should be documented. It is useful?
--
Bruce Momj
If so, does this also mean that if I have a single trigger defined as BEFORE
> UPDATE OR INSERT that this trigger will fire twice?
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/
hat if I have a single trigger defined as BEFORE
> UPDATE OR INSERT that this trigger will fire twice?
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
--
ice would no longer be subject to
> any of the RLS policies as long as she used the view instead of the real
> table.
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
mine the size of a temp table that
> will be entirely in memory.
Well, it depends what other temp tables are being accessed in the
session as to whether the table is completely in temp_buffers or
overflows to disk.
--
Bruce Momjian http://momjian.us
EnterpriseDB
On Tue, Jun 13, 2017 at 04:07:48PM -0400, Bruce Momjian wrote:
> On Fri, Jun 9, 2017 at 07:55:55AM -0700, Adrian Klaver wrote:
> I apologize for not being smarter on this thread. When I helped with
> the Windows port, I was told Windows didn't have hard links for use by
> table
re pg_upgrade was added to the tree, I
see that the code even at that time used hard links on Windows. I have
created the attached patch which I will apply to all current Postgres
versions to fix this error.
Thanks for the report and the research. :-)
--
Bruce Momjian http://momjian.us
e lines of the
> attached patch is what was intended.
I removed the duplicate text, and the referenced commit shouldn't appear
in the release notes.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I.
On Fri, May 12, 2017 at 07:42:27PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Tue, May 2, 2017 at 12:35:06PM -0400, Peter Eisentraut wrote:
> >> It has been pointed out a while ago that the "release date" formatting
> >> in the release notes is
e subdued. (Obviously,
> this needs to be expanded to older release notes as well.)
I see what you mean. I have changed the markup in head for all branches
and backpatched this so when we copy release information to back
branches, it matches.
--
Bruce Momjian http://
this
> point.
I think you are right that we don't support any constraint exclusion at
execution time, but using EXPLAIN should show you what it is doing.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.
time are displayED by EXPLAIN ANALYZE and
> are not displayED in other cases. The new EXPLAIN option SUMMARY allows
> explicit control of this.
Thank, fixED. :-)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ A
t; linked instead of copied.`
>
> It's debatable whether that sentence is unclear, I think, but the change
> you propose actually loses the information about what mode is the
> default, which wouldn't be good.
I have applied the attached doc patch to clarify this.
--
Bruce
On Mon, Apr 10, 2017 at 03:15:58PM -0400, Bruce Momjian wrote:
> On Fri, Apr 7, 2017 at 01:06:53PM -0400, Tom Lane wrote:
> > I actually think "regular" might be a better choice than "normal" for this
> > purpose, mainly because somebody looking for statisti
On Fri, Apr 7, 2017 at 01:06:53PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > This change is not on my patch yes but what do you think about changing
> > "regular" and "normal" aggregate designations to "generic"? That seems
> > cl
's too far away.
This change is not on my patch yes but what do you think about changing
"regular" and "normal" aggregate designations to "generic"? That seems
clearer because the aggregates work in non-window and window contexts.
--
Bruce Momjian htt
On Thu, Apr 6, 2017 at 06:43:38PM -0700, David G. Johnston wrote:
> On Thu, Apr 6, 2017 at 6:14 PM, Bruce Momjian wrote:
>
> On Thu, Apr 6, 2017 at 03:53:24PM -0700, David G. Johnston wrote:
>
> > hypothetical-set aggregates as being distinct from ordered
On Thu, Apr 6, 2017 at 03:53:24PM -0700, David G. Johnston wrote:
> On Thu, Apr 6, 2017 at 2:49 PM, Bruce Momjian wrote:
>
> As part of writing a talk about window functions, I have done some
> cleanups of the window function docs, attached, that I would like to
>
On Thu, Apr 6, 2017 at 06:13:44PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > As part of writing a talk about window functions, I have done some
> > cleanups of the window function docs, attached, that I would like to
> > apply to head.
>
> I thin
As part of writing a talk about window functions, I have done some
cleanups of the window function docs, attached, that I would like to
apply to head.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I
On Fri, Sep 23, 2016 at 08:31:02PM -0400, Bruce Momjian wrote:
> Nathan Wagner told me that two places in the create function docs say
> permissions are controlled by the function creator, while permissions
> are really controlled by the function owner.
>
> The attached patch fixes
On Wed, Nov 23, 2016 at 12:59:41PM -0500, Bruce Momjian wrote:
> On Tue, Nov 8, 2016 at 06:01:58PM +, d...@ringing.org wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/9.5/static/datatype-numeric
On Tue, Nov 22, 2016 at 06:17:35PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > On Thu, Oct 27, 2016 at 09:01:59PM -0400, Jason O'Donnell wrote:
> >> The example given for createdb fails because template0 is not provided:
>
> > I have looked over this repor
tecting such common values, and exclude them from the index automatically.
That is an interesting idea, but what happens if the table changes and
those values become rare? How would we adjust for that? What if the
table is empty when the index is created? How would we detect common
values?
--
B
Handling Large Databases
section. Why does it need fixing?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
--
Sent
On Tue, Jan 10, 2017 at 07:22:17AM +0900, Michael Paquier wrote:
> On Tue, Jan 10, 2017 at 4:32 AM, Bruce Momjian wrote:
> > On Sun, Jan 8, 2017 at 03:27:59PM +0900, Michael Paquier wrote:
> >> >> +subdirectory of both the current directory and the
> >
it if we decide to go that direction, though.
FYI, doc/src/sgml/README.links has instructions on how these markup
elements behave, or at least used to behave. We need to update that
file if it changed.
--
Bruce Momjian http://momjian.us
EnterpriseDB http:/
ists the five possible patterns: 2 for the case where a
> directory is defined, and 3 for the default case.
Understood. Here is an updated patch which incorporates your
suggestions.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.c
aken by the check
> routine. Just my 2c on the matter.
Ah, I see your point. I ended up rewording the text to be more explicit
about the supplied argument and "searching". Updated patch attached.
--
Bruce Momjian http://momjian.us
EnterpriseDB
On Tue, Dec 27, 2016 at 01:28:17PM +0900, Michael Paquier wrote:
> On Tue, Dec 27, 2016 at 6:56 AM, Bruce Momjian wrote:
> > I have found that pg_xlogdump looks for WAL files in the in the current
> > directory and the pg_wal subdirectory of both the current directory and
the
documentation. EXPLAIN will clearly show the index being used.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
-
I have found that pg_xlogdump looks for WAL files in the in the current
directory and the pg_wal subdirectory of both the current directory and
the PGDATA directory. Doc patch attached.
--
Bruce Momjian http://momjian.us
EnterpriseDB http
Infinity/-Infinity/NaN in the
> Data Types chapter the example would be better setting it to -Infinity
> rather than positive, as that would make clear that the minus sign needs to
> be within the quote marks. This isn't clear otherwise.
Is the attached patch what you are suggesting?
-
e common psql-like
options to control createdb. Adding the encoding is nice, but then
having to switch to template0 so the encoding setting works just seems
beyond the scope of what we want do there.
I think the attached patch is more focused.
--
Bruce Momjian http://momjian.us
Enterpr
On Fri, Sep 23, 2016 at 09:23:25PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > Nathan Wagner told me that two places in the create function docs say
> > permissions are controlled by the function creator, while permissions
> > are really controlled by the funct
Nathan Wagner told me that two places in the create function docs say
permissions are controlled by the function creator, while permissions
are really controlled by the function owner.
The attached patch fixes this.
--
Bruce Momjian http://momjian.us
EnterpriseDB
Back-patch to 9.6 and 9.5 as relevant.
Alexander Law
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman
l concerned about password "sniffing" attacks
> then md5 is
> preferred. '
> but how does this really help? If an md5 hash is enough to get access, then
> sniffing an md5has is actually the same as sniffing the password?'
There is random salt added to the net
e are some places in the docs where 'literal' is used for
> >>replaceable values. Patch attached.
> >Patch applied and backpatched to 9.6.
>
> Thanks!
> I've found some more places where usage is incorrect. Patch
> attached.
Patch applied
of -reuse-previous=on
> or -reuse-previous=off overrides that default.
> When the command neither specifies nor reuses a particular parameter,
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http:
; Skype has been using PostgreSQL as the main DB for most of our business
> needs right from the start.
> Hannu Krosing, Skype
> [
> Cheers
> Bernd
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
>
pplied to head.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresq
On Fri, Jul 22, 2016 at 08:35:32AM +0900, Michael Paquier wrote:
> On Fri, Jul 22, 2016 at 2:15 AM, Bruce Momjian wrote:
> > On Thu, Jul 21, 2016 at 10:11:00PM +0900, Michael Paquier wrote:
> >> + Copy all other files such as clog and
> >> clog is not a term used a
the docs. ISTM the following
> reads
> better:
>
> -don't know the details anyway.
> +aren't expected to know the details.
>
> Patch attached.
Thanks, patch applied.
--
Bruce Momjian http://momjian.us
EnterpriseDB ht
y adding new
fields.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
--
Sent via pgsql-docs mailing list (pgsql-docs@po
On Wed, Jul 13, 2016 at 09:18:05AM -0400, Stephen Frost wrote:
> * Alexander Law (exclus...@gmail.com) wrote:
> > I've found a hyphen missing in runtime.sgml. Patch attached.
>
> Fix pushed.
I have backpatched this to 9.1 as the original patch was backpatched.
--
Bruce M
On Thu, Jul 21, 2016 at 10:11:00PM +0900, Michael Paquier wrote:
> On Thu, Jul 21, 2016 at 3:07 AM, Bruce Momjian wrote:
> > I was confused by pg_rewind's ability to use a remote source server, and
> > another core team member was confused as well, so I figured I should
>
I was confused by pg_rewind's ability to use a remote source server, and
another core team member was confused as well, so I figured I should
update the pg_rewind docs to be clearer.
Attached is a patch to do that.
--
Bruce Momjian http://momjian.us
Enterpr
On Tue, Jun 28, 2016 at 05:21:51PM -0400, Bruce Momjian wrote:
> On Mon, Jun 20, 2016 at 11:16:36AM -0400, Bruce Momjian wrote:
> > In looking at the docs, it seems it would go in the Backup section
> > somewhere:
> >
> > https://www.postgresql.org/docs/9.6/static
nly major database system that I'm aware of that relies on
> operating system collations exclusively.
I am hopeful ICU has improved enough since we last researched that
support for it will soon be added.
--
Bruce Momjian http://momjian.us
EnterpriseDB htt
On Mon, Jun 20, 2016 at 11:16:36AM -0400, Bruce Momjian wrote:
> In looking at the docs, it seems it would go in the Backup section
> somewhere:
>
> https://www.postgresql.org/docs/9.6/static/backup.html
>
> Seems it would apply to both of these backup sections:
>
On Thu, Feb 18, 2016 at 07:19:57PM -0500, Bruce Momjian wrote:
> I have created the attached doc patch to update effective_io_concurrency
> to more accurately cover SSDs.
Patch applied.
--
Bruce Momjian http://momjian.us
EnterpriseDB
On Thu, Jun 23, 2016 at 09:25:26AM +0200, Magnus Hagander wrote:
>
>
> On Thu, Jun 23, 2016 at 3:32 AM, Bruce Momjian wrote:
>
> On Tue, Jun 21, 2016 at 08:15:35PM -0400, Tom Lane wrote:
> > Michelle Schwan writes:
> > > That sounds good (but in my
On Thu, Jun 23, 2016 at 07:47:10AM +0300, Dmitry Igrishin wrote:
> 2016-06-23 1:53 GMT+03:00 Bruce Momjian :
> > On Thu, Jun 9, 2016 at 03:38:40PM +0300, Dmitry Igrishin wrote:
> >> Hi,
> >>
> >> At https://www.postgresql.org/docs/9.6/static/protocol-flow.htm
t
> https://www.postgresql.org/docs/devel/static/ddl-depend.html
> in half an hour or so.
Uh, I don't think that builds every 30 minutes --- I think it is 4-6
hours. Comments?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpr
tion/publicapi/org/postgresql/PGRefCursorResultSet.html
>
> java.lang.String getRefCursor()
>
> Deprecated. As of 8.0, replaced with calling getString() on the ResultSet
> that this ResultSet was obtained from.
You need to contact the JDBC maintainers about this.
--
Bruce M
To begin a session, a frontend opens a connection to the server and
sends a startup message.
In that case, it is highlighting it is a startup message, not the exact
message identifier.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://e
of these places, but where can we
centrally put it?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
--
Sent via pgsql-doc
On Sat, Jun 18, 2016 at 08:26:30AM +0900, Michael Paquier wrote:
> On Sat, Jun 18, 2016 at 7:03 AM, Bruce Momjian wrote:
> > On Sat, Jun 18, 2016 at 06:36:45AM +0900, Michael Paquier wrote:
> >> On Sat, Jun 18, 2016 at 12:51 AM, Bruce Momjian wrote:
> >> > This pat
On Fri, Jun 17, 2016 at 06:01:59PM -0400, Bruce Momjian wrote:
> On Fri, Jun 17, 2016 at 05:51:54PM -0400, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > The attached patch documents that pg_upgrade requires old/new servers to
> > > use compatibile collati
On Sat, Jun 18, 2016 at 06:36:45AM +0900, Michael Paquier wrote:
> On Sat, Jun 18, 2016 at 12:51 AM, Bruce Momjian wrote:
> > This patch clarifies the documentation for when --source-pgdata and
> > --source-server can be used.
> >
> > I would like to apply this to 9.6.
On Fri, Jun 17, 2016 at 05:51:54PM -0400, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > The attached patch documents that pg_upgrade requires old/new servers to
> > use compatibile collation library versions as well.
>
> I think this is way too thin to be helpful:
Well,
This patch clarifies the documentation for when --source-pgdata and
--source-server can be used.
I would like to apply this to 9.6.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will
The attached patch documents that pg_upgrade requires old/new servers to
use compatibile collation library versions as well.
I would like to apply this to all PG branches.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you
I have created the attached doc patch to update effective_io_concurrency
to more accurately cover SSDs.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave
the index diverge :)!
We issue a warning on hash index creation in 9.5:
Issue a warning during the creation of hash indexes because they are not
crash-safe (Bruce Momjian)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
On Tue, Dec 1, 2015 at 01:22:25PM +0100, Michael Herold wrote:
> On 01/12/15 00:59, Bruce Momjian wrote:
> >I would argue that '{}'::int[] is zero dimmensions, so there is no
> >documented behavior for this.
>
> Thank you for your reply. Agree, I am writing to pg
-empty one as the result
*
* if both are empty, return the first one
*/
if (ndims1 == 0 && ndims2 > 0)
PG_RETURN_ARRAYTYPE_P(v2);
I doubt we want to change this.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+
d it has a great quality.
> We (bitnine) plan, lead and invest for translating and publish the book.
I can write something if you wish.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so
On Mon, Oct 5, 2015 at 08:19:26PM -0400, Bruce Momjian wrote:
> In studying our JSONB operators, I was confused about what they do based
> on the docs. I found that "contain within" means "contain the
> path/value", i.e. it has to match the path from the top level, n
On Wed, Aug 26, 2015 at 10:02:26PM -0400, Bruce Momjian wrote:
> On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote:
> > http://www.postgresql.org/docs/devel/static/app-psql.html
> >
> > The other pset keywords with black-slash aliases include a "(or )&qu
;a":1, "c" : {"b":2}}'::jsonb @> '{"d":{}}'::jsonb;
?column?
--
f
I also found that "key/element string exist" really means "string exist
as a top-level key", e.g.
SELECT &#
On Sat, May 16, 2015 at 08:37:59AM -0400, Bruce Momjian wrote:
> We have made major improvements in GIN in the past few releases,
> particularly 9.4, but the full text search docs recommending when to use
> GIN and GiST indexes have not been updated. This blog post empirically
> shows
ocumentation series the same
> (9.1,9.2,9.3,9.4...).True usage is;
>
> ALTER FOREIGN TABLE myschema.distributors OPTIONS (ADD opt1 'value', SET opt2
> 'value2', DROP opt3 'value3');
This has been fixed, thanks.
--
Bruce Momjian http://momjian.us
Ent
gt; > seriously, e.g. on stackoverflow[1], how about we remove this outdated
> > suggestion? There is already a previous mention a few sections
> > earlier[2] suggesting the use of CONCURRENTLY, so I don't think we
> > really need to reiterate that suggestion here.
>
ing "\pset C " work doesn't seem like an improvement.
Well, making \pset C is at least consistent. We can't say "or C"
without it.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own
On Wed, Aug 26, 2015 at 10:51:09PM -0400, David G. Johnston wrote:
> On Wed, Aug 26, 2015 at 10:02 PM, Bruce Momjian wrote:
>
> On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote:
> > http://www.postgresql.org/docs/devel/static/app-psql.html
> >
&
t;)
Attached is a patch to implement this, including a doc patch.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
n
On Sun, Jun 14, 2015 at 10:49:04AM +0100, Dean Rasheed wrote:
> There's a minor grammatical typo in the description of leakproof
> functions (going back to 9.2).
> Patch attached.
Patch applied and backpatched to 9.5 --- thanks.
--
Bruce Momjian http://momjian.us
On Thu, Jun 11, 2015 at 10:53:51PM -0400, Bruce Momjian wrote:
> On Thu, Jun 11, 2015 at 10:51:25PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > I see 34 instance of "=>" in our docs. Shouldn't the '>' be escaped,
> > > e.g. =&g
In SGML, does anyone know how to add a new tag, , and cause
it to use smallcaps (https://en.wikipedia.org/wiki/Small_caps)?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql
On Thu, Jun 11, 2015 at 10:51:25PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I see 34 instance of "=>" in our docs. Shouldn't the '>' be escaped,
> > e.g. =>?
>
> In principle, yes, though you can often get away with this as long
I see 34 instance of "=>" in our docs. Shouldn't the '>' be escaped,
e.g. =>?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-docs mailing l
-since-postgresql-7-4-to-9-4-fulltext
I would like to apply the attached patch to 9.5 to recommend GIN indexes
for full text search, and remove mention of many old GIN limitations.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
On Wed, Apr 29, 2015 at 04:08:15PM -0400, Bruce Momjian wrote:
> On Wed, Apr 29, 2015 at 02:15:20PM +, Kevin Grittner wrote:
> > Bruce Momjian wrote:
> >
> > > I went with "Allowed, but not in PG" for those two fields, and
> > > removed the extr
27;ve refactored this slightly to put the installation details at the top, and
> remove the term "system view".
Patch applied, thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
On Wed, Apr 29, 2015 at 02:15:20PM +, Kevin Grittner wrote:
> Bruce Momjian wrote:
>
> > I went with "Allowed, but not in PG" for those two fields, and
> > removed the extra rows I had added. You can see the output here:
> >
> > http:
On Fri, Feb 6, 2015 at 04:52:54PM +1100, Craig Ringer wrote:
> We've had server_version_num since 8.2.
>
> Advise devs to prefer to use it instead of parsing version() or server_version
Patch applied.
--
Bruce Momjian http://momjian.us
On Sat, Apr 25, 2015 at 02:14:37PM -0700, David G. Johnston wrote:
> On Saturday, April 25, 2015, Bruce Momjian wrote:
>
> On Sat, Apr 25, 2015 at 08:47:47PM +, Kevin Grittner wrote:
> > Maybe something like "Prohibited", "Allowed but not Possible&q
d then the monitor column would distinguish
> between repeatable read and serializable.
I think the showing a serialization failure column is too much to add to
the table.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ E
he standard's table
> in its word choice.
I can't even process that.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-docs mailing list (pgsql-docs@p
possible, PostgreSQL not possible", but that is too
long. This is why I split it into separate lines. We could try
"Possible (SQL standard), Not possible (PostgreSQL)".
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
On Sat, Apr 25, 2015 at 11:33:36AM -0700, David G. Johnston wrote:
> On Sat, Apr 25, 2015 at 11:02 AM, Bruce Momjian wrote:
>
> On Fri, Apr 24, 2015 at 08:40:40PM +, Kevin Grittner wrote:
> > And, for reasons given above, I really question whether such a
> >
rounding text to more clearly reference the table. You
can see the output here, and the SGML patch is attached:
http://momjian.us/expire/transaction-iso.html
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has
stgres implementation. Should I write a patch or would you like to?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To
On Wed, Apr 1, 2015 at 04:52:48PM -0400, Bruce Momjian wrote:
> On Fri, Dec 19, 2014 at 06:52:42PM -0700, David Johnston wrote:
> > While the fact that you cannot do:
> >
> > [service_template]
> > host=xxx.xxx.xxx.xxx
> >
> > [service_db1]
>
to hunt in the documentation. I don't
think this issue has come up enough to warrant a doc mention too though.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
diff --git a/src/interfaces/libpq/
http://docbook.org/tdg/en/html/xref.html).
>
> I can't seem to make an render the ...
> element text. The DocBook documentation implies that this should be the
> default; e.g. if you have:
Have you read README.links in the sgml top-level directory?
--
I'm not sure if that's the standard's
> terminology; but ISTM that if we consistently referred to the Ixxx
> format specifiers as "ISO week-numbering foo" then this type of error
> might become a little less attractive.
>
> Objections, better ideas?
unlimited
>@hugepages hardmemlock unlimited
>
> In some cases (e.g. Debian's start-stop-daemon) the command "ulimit
> -l unlimited" may be needed in the PostgreSQL startup scripts
> instead of the limits.conf edit, because PAM
1 - 100 of 1147 matches
Mail list logo
