he codes in ascending sequence?
> This applies to all releases.
Uh, I am guessing this is the order listed in the SQL standard. How
would you order them differently? Have the letters only at the end?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
acestrunc(42.4382, 2) 42.43
Uh, Postgres 7.1 is _decades_ old and will not be fixed. I suggest you
look at the Postgres 10 docs.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb
upgrade
> mechanism, ensuring I do not loose time nor any data).
> Thanks for your efforts to offer Postgres to the IT community!
This is really something for you to address with Ubuntu. The Postgres
community provides the tools, but the user interface is often up to the
packag
and backpatched through 9.3. Thanks.
--
Bruce Momjian <br...@momjian.us>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 +
On Tue, May 1, 2018 at 10:14:48AM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > Our release.sgml contains these lines, that I wrote:
> > we cannot use UTF8 because SGML Docbook does not support it
> > do not use numeric _UTF_ numeric character escapes (
<
On Thu, Jan 18, 2018 at 12:17:40PM +0900, Michael Paquier wrote:
> On Wed, Jan 17, 2018 at 09:00:17PM -0500, Bruce Momjian wrote:
> > On Thu, Jan 18, 2018 at 10:25:03AM +0900, Michael Paquier wrote:
> > > /etc/ssl/openssl.cnf is not available on macos or Windows, which can
&
r in a where clause, e.g. WHERE col ~ 'ab.*c'. Not sure how we can
improve the docs here.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+
On Wed, Jan 17, 2018 at 07:34:42AM -0500, Bruce Momjian wrote:
> > The succession of commands of commands for the intermediate certificates
> > is wild. Could it be possible to explain what each command means? Users
> > would not get lost this way.
>
> Yes, I was not hap
> It would be clearer if the documentation covered all three cases:
> 9.6.3 - 10.0.0 and 9.5.1 - 9.6.3: pg_upgrade should be used
> 9.6.2 - 9.6.3: pg_upgrade not needed
>
> Or if the documentation simply noted that the second decimal is considered a
> major release.
How is t
On Thu, Jan 11, 2018 at 08:13:28PM +0300, Oleg Bartunov wrote:
> On Thu, Jan 11, 2018 at 7:22 PM, Bruce Momjian <br...@momjian.us> wrote:
> > On Tue, Oct 24, 2017 at 08:18:49PM +, torsten.gr...@gmail.com wrote:
> >> The following documentation comment has be
On Tue, Jan 30, 2018 at 05:30:59PM +0300, Pavel Luzanov wrote:
> On 30.01.2018 16:08, Bruce Momjian wrote:
>
> The most current keyworsd list is in our source tree:
>
> And this list is accessible through the pg_get_keywords() function.
Sorry, yes, I forgot we added that lo
26af944e03a1109210d36060fc9acebc1b6ffa20;hb=HEAD
However, that doesn't have TIMESTAMPTZ or JSON because those are data
types, not keywords.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterpris
umbers
so I have added major and minor examples for the 9.6.x series and 10.x
series releases. Patch attached.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you wil
On Sun, Jan 28, 2018 at 02:18:38PM -0500, Tom Lane wrote:
> Thomas Munro <thomas.mu...@enterprisedb.com> writes:
> > On Thu, Jan 25, 2018 at 11:07 AM, Bruce Momjian <br...@momjian.us> wrote:
> >> ... The attached patch updates the docs to say
> >> statement
On Sun, Jan 28, 2018 at 03:57:07PM -0500, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > Uh, I don't think we want to highlight the statement vs row difference
> > here but the fact that statement triggers fire on the referenced object
> > and not on
On Thu, Jan 25, 2018 at 12:46:52PM -0500, Bruce Momjian wrote:
> I propse the attached patch to fix the generic syntax and the example.
> I will backpatch it through 9.5. As you stated, the tablespace example
> is fine.
Done. Thanks for the report.
--
Bruce Momjian <br..
On Sun, Jan 28, 2018 at 06:17:19PM -0500, Bruce Momjian wrote:
> On Sun, Jan 28, 2018 at 06:12:01PM -0500, Tom Lane wrote:
> > Bruce Momjian <br...@momjian.us> writes:
> > > Oh, I am sorry. I was focused on the first part of the sentence and
> > > didn't noti
On Mon, Jan 29, 2018 at 09:31:46PM -0500, Jim Ryan wrote:
> This looks great. Thanks for working on it.
Done.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I a
On Mon, Jan 29, 2018 at 11:03:32PM -0500, Bruce Momjian wrote:
> On Mon, Jan 29, 2018 at 08:58:10PM -0700, David G. Johnston wrote:
> > On Mon, Jan 29, 2018 at 8:55 PM, Bruce Momjian <br...@momjian.us> wrote:
> >
> > On Mon, Jan 29, 2018 at 10:51:59PM -0500, Tom
ine
>
> the spi acronym.
>
> Seems reasonable.
How is the attached patch?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+
On Mon, Jan 29, 2018 at 08:39:22PM -0700, David G. Johnston wrote:
> On Monday, January 29, 2018, Bruce Momjian <br...@momjian.us> wrote:
>
>
> How is the attached patch?
>
>
>
> Maybe add a link to:
>
> https://www.postgresql.org/docs/10/sta
On Mon, Jan 29, 2018 at 10:51:59PM -0500, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > How is the attached patch?
>
> Maybe also make that text into a hyperlink to the SPI manual chapter?
Yes, that's what I just did in the new patch.
--
Bruce Momji
On Mon, Jan 29, 2018 at 08:58:10PM -0700, David G. Johnston wrote:
> On Mon, Jan 29, 2018 at 8:55 PM, Bruce Momjian <br...@momjian.us> wrote:
>
> On Mon, Jan 29, 2018 at 10:51:59PM -0500, Tom Lane wrote:
> > Bruce Momjian <br...@momjian.us> writes:
>
ld VALUES (2, 'two');
--> NOTICE: Called by child INSERT
INSERT 0 1
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Anci
if "go dig in the git repo" doesn't seem like an adequate answer
> for that.
>
> Works for me. Especially with a release note archive available somewhere.
Works for me, though, is there no interest in keeping the SGML files in
the git tree and just not building them as docs?
--
On Thu, Aug 9, 2018 at 10:14:33AM -0400, Bruce Momjian wrote:
> On Thu, Aug 9, 2018 at 12:18:27PM +1200, Morgan Owens wrote:
> > On 2018-08-09 05:24, Bruce Momjian wrote:
> > >On Mon, Jul 23, 2018 at 09:14:48AM +, PG Doc comments form wrote:
> > >>The following
width=8) (actual rows=100
loops=1)
The second query has it right:
Seq Scan on t (cost=0.00..195.00 rows=100 width=8) (actual rows=100
loops=1)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpris
cumentation states "6 decimal
> digits precision" for the real type, we are talking about 6 digits after the
> decimal point or 6 digits in total (before and after)?
Well the number is stored as a mantissa and exponent, so it is 6
mantissa digits plus an exponent from 1E-37 to 1E+37.
would cause the
row to be inserted into the referenced table.
--
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 +
ng in the chapter about PREPARE
> https://www.postgresql.org/docs/current/static/sql-prepare.html or about the
> backend protocol:
> https://www.postgresql.org/docs/current/static/protocol.html nor on the FAQ
> page: https://wiki.postgresql.org/wiki/FAQ
Uh, is this something people
o just several major versions as long as they read the
release notes of all the versions they skipped. Shipping all active
major version release notes works for that.
Personally, I would find a git tree or tarball of all release notes in
SGML or HTML format useful.
--
Bruce Momjian http://mo
espaces(),
describeTypes(), listAllDbs(), listDefaultACLs(), listDomains(),
listForeignDataWrappers(), listForeignServers(), listLanguages(),
listSchemas(), and permissionsList().
so we would need to list _all_ of these uses, which I don't think we
want to do.
--
Bruce Mom
ry, as mentioned above." Note that the global dictionary is named
> "SD" in the first quote and "GD" in the second one.
>
> Please correct either first or second sentence.
Well, the documentation is correct, but obviously not clear. I have the
attached patch which modif
assed
> through
> > as a group.
I see your point. We call 'postgres' binary options 'options' and we
call initdb-mode options 'initdb-options' in the -o title, but not in
the paragraph. I assume we want to keep calling the former simply
'options'.
--
Bruce Momjian http:
On Fri, Aug 24, 2018 at 08:43:21PM +0200, Adam wrote:
> Yes, it does, thank you.
>
> Now it's clear why there are two different names.
Patch backpatched through 9.3. Thanks for the report.
--
Bruce Momjian http://momjian.us
EnterpriseDB
On Fri, Aug 24, 2018 at 04:47:28PM -0400, Bruce Momjian wrote:
> I see your point. We call 'postgres' binary options 'options' and we
> call initdb-mode options 'initdb-options' in the -o title, but not in
> the paragraph. I assume we want to keep calling the former simply
> 'opti
only document it in SELECT, which is
odd. I think that is because the SQL standard only uses WITH with
SELECT.
--
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 +
On Sat, Sep 1, 2018 at 07:30:43PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > Looking over the AT TIME ZONE docs, I think they are subtly confusing.
> > The order of conversion specific in the first example should _start_
> > with the assumption of local time zo
On Sat, Sep 1, 2018 at 07:37:36PM -0400, Bruce Momjian wrote:
> > Here we've got a time value that was initially given in EST (-05),
> > but was converted to UTC by timestampz_in. Then the AT TIME ZONE
> > says "Please convert this UTC value to MST, and emit it as a
the second example confusing too.
The attached patch fixes this.
--
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 +
diff
On Mon, Sep 3, 2018 at 09:20:34AM -0400, Bruce Momjian wrote:
> On Sun, Sep 2, 2018 at 10:11:59PM -0400, Bruce Momjian wrote:
> > On Sun, Sep 2, 2018 at 02:21:58PM -0400, Tom Lane wrote:
> > > I still find this to be more confusing than helpful. In particular,
> > &g
On Thu, Sep 6, 2018 at 06:45:29PM +0300, Liudmila Mantrova wrote:
>
> On 08/25/2018 10:04 PM, Bruce Momjian wrote:
> >On Thu, Aug 16, 2018 at 11:25:25AM +0300, Liudmila Mantrova wrote:
> >>On 06/20/2018 05:04 PM, Magnus Hagander wrote:
> >> I have spl
meaning you can grant group role membership to user and other group
roles.
--
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 +
On Thu, Jun 28, 2018 at 09:32:23AM -0400, Bruce Momjian wrote:
> On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote:
> > Hello,
> >
> > Could we please add Pgfe client library to the external interfaces section?
> >
> > Patch is attached.
On Wed, Jan 17, 2018 at 05:20:00PM +0900, Michael Paquier wrote:
> On Tue, Jan 16, 2018 at 10:23:44PM -0500, Bruce Momjian wrote:
> > On Wed, Jan 17, 2018 at 09:09:50AM +0900, Michael Paquier wrote:
> > > On Tue, Jan 16, 2018 at 11:21:22AM -0500, Bruce Momjian wrote:
> >
is a new patch, which removed the whole sentence with example link.
Patch applied and backpatched through 9.3. Thanks.
--
Bruce Momjian <br...@momjian.us>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 +
>) is about 240 bytes.
> + url="http://www.dmoztools.net;>) is about 271 bytes.
>
>
>
Patch applied back through 9.3. Thanks.
--
Bruce Momjian <br...@momjian.us>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 +
h! It seems to be an oversight in commit
> 768b647ead78d0d63915c1708cad13c2468f9440. The attached patch adds it.
Wow, that commit is from 2004. Patch applied and backpatched to v10.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://ent
an oversight.
> Should we repeat the statement in another item (like the attached
> patch)? Another option is to add a statement in the "IS DOCUMENT"
> item. I'm afraid that NULL return wouldn't be clear.
>
Patch applied and backpatched to Postgres 10. Thank.s
--
Bruce Momjian
On Fri, Mar 30, 2018 at 05:39:46PM +0200, Magnus Hagander wrote:
> On Fri, Mar 30, 2018 at 5:18 PM, Bruce Momjian <br...@momjian.us> wrote:
>
> On Fri, Mar 16, 2018 at 01:17:04AM -0300, Euler Taveira wrote:
> > 2018-03-11 1:43 GMT-03:00 PG Doc comments form &l
On Fri, Mar 30, 2018 at 10:31:07AM -0700, David G. Johnston wrote:
> On Friday, March 30, 2018, Bruce Momjian <br...@momjian.us> wrote:
>
> I looked at this patch and thought it was more a stylistic item rather
> than a correction. Is that right?
>
>
> Looks
On Fri, Mar 30, 2018 at 06:28:15PM +0200, Magnus Hagander wrote:
> On Fri, Mar 30, 2018 at 6:26 PM, Bruce Momjian <br...@momjian.us> wrote:
> Uh, I am always debating how important it is to backpatck vs the churn
> we require of translations of our docs. In this case,
condition="standalone-ignore" attribute.
I have fixed it by using "standalone-ignore" in the attached, applied
patch.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you
On Mon, Apr 2, 2018 at 11:51:50AM -0400, Peter Eisentraut wrote:
> On 3/30/18 10:40, Bruce Momjian wrote:
> > On Fri, Mar 16, 2018 at 01:56:32AM -0300, Euler Taveira wrote:
> >> 2018-03-09 0:10 GMT-03:00 PG Doc comments form <nore...@postgresql.org>:
> >>> Fr
on, I have developed the attached patch which
tries to clarify the behavior without adding complexity.
If this is applied, should it be backpatched as a fix?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As yo
e allowed range draw an
error. float with no precision specified is taken to mean double
precision.
Adding float() to that chart seems like it would add too much complexity.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
On Mon, Apr 2, 2018 at 08:21:45PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > Based on this discussion, I have developed the attached patch which
> > tries to clarify the behavior without adding complexity.
>
> I don't think thi
s.
Discussion:
https://postgr.es/m/152199346794.4544.1888397173908716...@wrigleys.postgresql.org
--
Bruce Momjian <br...@momjian.us>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 +
tion
>
> how does the jsonb_set function work?
> does it create a whole new json and updates it in the column? or it actually
> only updates the specific key in "path"
jsonb_set() is a function that returns a JSONB value with the fields
changed. It is up to you to assign i
gml/external-projects.sgml
> +++ b/doc/src/sgml/external-projects.sgml
> @@ -83,6 +83,13 @@
>
>
>
> + Pgfe
> + C++
> + An API inspired by libpq
> + https://github.com/dmitigr/pgfe;>
> +
> +
> +
>node
On Thu, Jun 28, 2018 at 04:03:36PM +0200, Daniel Gustafsson wrote:
> > On 28 Jun 2018, at 15:32, Bruce Momjian wrote:
> >
> > On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote:
> >> Hello,
> >>
> >> Could we please add Pgfe clie
On Thu, Oct 11, 2018 at 03:56:42PM -0300, Peter Krauss wrote:
>
> The page https://www.postgresql.org/docs/10/static/functions-admin.html
> need this information, is like a "pg_read_file Guide".
>
>
> On Thu, Oct 11, 2018 at 3:51 PM Bruce Momjian wrote:
>
>
ot;not" and "any" is confusing. I can reword this last line to be:
The result is NULL if no comparison with a subquery row returns
false, and it returns NULL for at least one row.
I can make similar adjustments in other places, and have attached a doc
patch. D
rs in both places that has led
many to ignore the shared buffer size in computing effective_cache_size.
So, I think there are two action items here. First, rename "disk" to
"drive" or "storage" in the docs and server variable descriptions.
Second, unify the descripti
reader need it.
Uh, add data_directory where? Which guide?
--
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 +
comparison has two row sets --- the left-hand side, and the right-hand
side. Each row on the left-hand side is compared with the row set on
the right. I also don't like people thinking about the result of ANY
since it is really ANY that is being used.
--
Bruce Momjian http://momjian.us
On Fri, Oct 12, 2018 at 02:37:33PM -0700, David G. Johnston wrote:
> On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian wrote:
>
> Sorry, but I don't like this wording. The problem is that the
> comparison has two row sets --- the left-hand side, and the right-hand
> si
"unknown" in this context, if possible.
---
> 13.10.2018, 00:37, "David G. Johnston" :
>
> On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian wrote:
>
> Sorry, but I don't like this wording. The
n.com"
>
> Is there any reason why our doc recommend the two-step procedure?
This was changed as part of this commit:
commit 815f84aa166de294b80e80cc456b79128592720e
Author: Bruce Momjian
Date: Sat Jan 20 21:47:02 2018 -0500
doc: update intermediat
ERROR: RETURN cannot have a parameter in a procedure
--> LINE 5: RETURN NULL;
^
CREATE OR REPLACE PROCEDURE triple()
LANGUAGE plpgsql
AS $$
BEGIN
RETURN;
END;
$$;
--
Bruce Momjian
On Thu, Oct 11, 2018 at 01:48:49PM -0400, Bruce Momjian wrote:
> So, I think there are two action items here. First, rename "disk" to
> "drive" or "storage" in the docs and server variable descriptions.
> Second, unify the description of effective_cache_
r geometric types don't know anything about
longitude or latitude. PostGIS does handle this, but it is a separate
project team.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
On Mon, Nov 5, 2018 at 12:50:01PM +0100, Peter Eisentraut wrote:
> On 16/10/2018 17:38, Bruce Momjian wrote:
> > diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c
> > index 2317e8b..e471d7f 100644
> > --- a/src/backend/utils/misc/guc.c
> > +++ b/s
On Mon, Oct 15, 2018 at 12:32:20PM -0400, Bruce Momjian wrote:
> On Sun, Oct 14, 2018 at 11:00:18PM -0700, David G. Johnston wrote:
> > On Saturday, October 13, 2018, Bruce Momjian wrote:
> >
> > On Sat, Oct 13, 2018 at 12:25:38PM +0300, KES wrote:
>
On Tue, Oct 16, 2018 at 11:38:20AM -0400, Bruce Momjian wrote:
> On Thu, Oct 11, 2018 at 01:48:49PM -0400, Bruce Momjian wrote:
> > So, I think there are two action items here. First, rename "disk" to
> > "drive" or "storage" in the docs and ser
On Mon, Nov 5, 2018 at 03:23:03PM +0300, Nikolay Samokhvalov wrote:
>
>
> On Mon, Nov 5, 2018 at 3:01 PM Bruce Momjian wrote:
>
> > > {"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
> > > - gettext_n
On Mon, Nov 5, 2018 at 02:01:12PM -0300, Alvaro Herrera wrote:
> On 2018-Nov-05, Bruce Momjian wrote:
>
> > Well, here are the lines in guc.c:
> >
> > gettext_noop("Sets the planner's assumption about the size of
> > the data cac
functions without
> SHOW data_directory
What do you mean by that? I can call pg_read_file() before calling
'SHOW data_directory'. Are you saying that pg_read_file can only read
in the data_directory? It is designed that way.
--
Bruce Momjian http://momj
fOn Sun, Sep 2, 2018 at 02:21:58PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > ! The AT TIME ZONE construct allows the addition,
> > ! conversion, and removal of time zones for time stamp values. > linkend="functions-datetime-zonecon
in your academic studies? If yes: in which chapter?
>
> Who's to say that every single reader of the PG documentation has had
> relevant academic studies? My opinion is that these graphics are worth
> including even if they're well-known to many.
Agreed. Indexing methods are myste
;
> b) Is it worth to visualize PG's tree-implementation in a separate graphic -
> or is it the same as in every other tree-implementation that you have
> learned in your academic studies? If yes: in which chapter?
I am CC'ing Oleg, Teodor, and Alexander, who can answer the first
q
ocess we all agreed with. Should we move ahead and commit some of
these diagrams to the souce tree for PG 12?
--
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 +
sql citext documentation
> (https://www.postgresql.org/docs/10/citext.html) is needed until this is
> fixed.
> Case insensitive text is standard on many databases, thus this may be a big
> obstacle when you want to migrate.
You have not explained what "does not work" means.
--
note underscore is included)
Frankly, I can't even guess what you expect \q to do.
--
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 +
; on
> the first SVG source files. 'Copy' is widely used and the first
> examples will have the meaning of a lighthouse.
> • I will contact our web-team to discuss style-guide related issues.
Sounds good. I have many xfig/SVG images in my presentations if you
want to u
SERT function when nested, does
> not propagate the return value up, and causes a syntax error on the "INTO"
> keyword, this is because the RETURNING extension is also expecting in "INTO"
> key word, which isn't mentioned anywhere in the documentation?
Uh, can you show us
ndexes-unique.html there are
> omited clausules
>
> For example WHERE clausule is omited.
>
> In https://www.postgresql.org/docs/11/static/sql-createindex.html you can
> see the right sintax with all the clausules.
The first URL is an example and is not intended to be the c
he pgpass case, we have a default location, while in the
service file case, we rely on the output of 'pg_config --sysconfdir'.
We don't specify the location of the service file on Unix-like systems
either. Should this be changed?
--
Bruce Momjian http://momjian.us
EnterpriseDB
ed back through 9.4.
--
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 +
is the same architecture ...
I feel we might have cases where differences beyond the CPU might
matter, though I can't think of any now.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so y
.
As far as rendering in HTML, I think we have two choices:
1. make images a link to an SVG file that can be rendered in a new
browser tab
2. convert the SVG to PNG for HTML rendering.
I kind of prefer #2.
--
Bruce Momjian http://momjian.us
EnterpriseDB
On Wed, Nov 28, 2018 at 01:05:28PM -0500, Bruce Momjian wrote:
> On Wed, Nov 28, 2018 at 06:34:26PM +0100, Jürgen Purtz wrote:
> > After one week no response at all? Neither positive nor negative. It seems
> > that
> > the community has little interest in the SVG issue
; > suggestion?
>
> I'd suggest describing your proposed workflow in sgml, not a pdf file.
Well, there were a number of images in the PDF that would be harder to
do in SGML.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb
) &< int8range(100,110);
?column?
--
t
SELECT int8range(1,105) &< int8range(100,110);
?column?
--
t
SELECT int8range(1,200) &< int8range(100,110);
?column?
df', true);
current_setting
-
\pset null (null)
SELECT current_setting('asdf', true);
current_setting
-
--> (null)
How do you like the attached patch, which clarifies this?
--
Bruce Momjian
start to
> center and from end to center.
> +
> +
> diff --git a/doc/src/sgml/svg/gin.svg b/doc/src/sgml/svg/gin.svg
> new file mode 100644
> index 00..8a5e77b252
> --- /dev/null
> +++ b/doc/src/sgml/svg/gin.svg
> @@ -0,0 +1,123 @@
> + xmlns="http://www.w3.or
On Fri, Jan 25, 2019 at 10:39:28AM +0100, Peter Eisentraut wrote:
> On 24/01/2019 00:53, Bruce Momjian wrote:
> > This is a pretty complicated issue with a lot of back-story. I am
> > thinking Tatsuo or me will probably commit it before March.
>
> Isn't that all t
content at those two URLs. I don't understand your
question.
--
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 +
t; than keeping the actual release notes in each tarball.
I assume this means we would only keep the current release notes in the
git tree too, e.g. 11.0, 11.1, 11.2, etc.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so on
le --- it is too dense and
confusing. I liked your sub-bullets. I adjusted your patch to tighten
the language, and reordered the entries to appear in the order the
actions would be performed.
Updated patch attached.
--
Bruce Momjian http://momjian.us
EnterpriseDB
1 - 100 of 670 matches
Mail list logo
