On Mon, Oct 30, 2017 at 6:08 AM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/collation.html
> Description:
>
> By design, ICU will accept almost any string as a locale name and match it
> to the _closet_ locale i
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/collation.html
Description:
By design, ICU will accept almost any string as a locale name and match it
to the _closet_ locale it can provide...
--
Sent via pgsql-docs mailing list
On 2017-10-23 10:41, juer...@purtz.de wrote:
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/app-pgdump.html
Description:
There is a typo at "the old locution" (since 8.2) - probable
shall be "the
old location".
Your 'correct
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/app-pgdump.html
Description:
There is a typo at "the old locution" (since 8.2) - probable shall be
"the
old location".
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.
On Sun, Oct 15, 2017 at 8:21 PM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/release-10.html
> Description:
>
> "The UNENCRYPTED option is no longer supported in CREATE/ALTER USER
> ...
> PASSSWORD."
>
That's cu
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/release-10.html
Description:
"The UNENCRYPTED option is no longer supported in CREATE/ALTER USER ...
PASSSWORD."
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To
On Thu, Oct 5, 2017 at 9:36 PM, Oleksandr Pikozh wrote:
> https://www.postgresql.org/about/featurematrix/detail/292/
>
> > Ability to automatically pull in required additional extensions for an
> extension dedpendency tree.
> dedpendency -> dependency
Fixed, thanks for the report!
--
Magnus
https://www.postgresql.org/about/featurematrix/detail/292/
> Ability to automatically pull in required additional extensions for
an extension dedpendency tree.
dedpendency -> dependency
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http
2017-05-23 7:40 GMT-03:00 :
>
> I believe that ("statement" is wrong):
>
> "Row-level BEFORE triggers fire immediately before a particular row is
> operated on, while row-level AFTER triggers fire at the end of the
> statement
> (but before any statement-level AFTER triggers)."
>
>
> should be:
>
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/9.6/static/trigger-definition.html
I believe that ("statement" is wrong):
"Row-level BEFORE triggers fire i
On Wed, May 17, 2017 at 6:13 AM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/ddl-constraints.html
> Description:
>
> https://www.postgresql.org/docs/9.6/static/ddl-constraints.html#DDL-
> CONSTRAINTS-FK
>
> "If
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/ddl-constraints.html
Description:
https://www.postgresql.org/docs/9.6/static/ddl-constraints.html#DDL-CONSTRAINTS-FK
"If someone removes an order, the order items are removed as w
Dmitry Igrishin writes:
> 2016-06-07 15:44 GMT+03:00 Kevin Grittner :
>> I'm pretty sure that this has been discussed on this list before
>> and decided in favor of omitting the hyphenation in such cases.
> Hm, well, how about removing hypenation from
> "Internal query: the text of a failed inter
2016-06-07 16:47 GMT+03:00 Tom Lane :
> Dmitry Igrishin writes:
>> 2016-06-07 15:44 GMT+03:00 Kevin Grittner :
>>> I'm pretty sure that this has been discussed on this list before
>>> and decided in favor of omitting the hyphenation in such cases.
>
>> Hm, well, how about removing hypenation from
On Tue, Jun 7, 2016 at 8:22 AM, Dmitry Igrishin wrote:
> 2016-06-07 15:44 GMT+03:00 Kevin Grittner :
>> On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin wrote:
>>
>>> In "Internal position: this is defined the same as the P field, but it
>>> is used when the cursor position refers to an internally
2016-06-07 15:44 GMT+03:00 Kevin Grittner :
> On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin wrote:
>
>> In "Internal position: this is defined the same as the P field, but it
>> is used when the cursor position refers to an internally generated",
>> "internally generated" should be replaced with
On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin wrote:
> In "Internal position: this is defined the same as the P field, but it
> is used when the cursor position refers to an internally generated",
> "internally generated" should be replaced with "internally-generated".
Not according to, for ex
2016-06-07 14:26 GMT+03:00 Dmitry Igrishin :
> Hi,
>
> In "Internal position: this is defined the same as the P field, but it
> is used when the cursor position refers to an internally generated",
> "internally generated" should be replaced with "internally-generated".
> https://www.postgresql.org/
Hi,
In "Internal position: this is defined the same as the P field, but it
is used when the cursor position refers to an internally generated",
"internally generated" should be replaced with "internally-generated".
https://www.postgresql.org/docs/9.6/static/protocol-error-fields.html
--
// Dmitr
Michael Paquier writes:
> On Sat, Jun 4, 2016 at 4:28 PM, wrote:
>> Before restoring an SQL dump,
>> Should be
>> Before restoring a SQL dump,
> The source code has a shared opinion on the matter:
> $ git grep "a SQL" | wc -l
> 630
> $ git grep "an SQL" | wc -l
> 238
> Based on some past memori
On Sat, Jun 4, 2016 at 4:28 PM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.5/static/backup-dump.html
> Description:
>
> Before restoring an SQL dump,
>
> Should be
>
> Before restoring a SQL dump,
The source code has a
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/backup-dump.html
Description:
Before restoring an SQL dump,
Should be
Before restoring a SQL dump,
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make chang
"David G. Johnston" writes:
> The second closing bracket after "connlimit" should be moved after
> "istemplate ]"
Hm, yeah, somebody fat-fingered that. Will fix, thanks.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes
The second closing bracket after "connlimit" should be moved after
"istemplate ]"
The IS_TEMPLATE option can be prefixed by "WITH" when used alone.
i.e., create database newdb with is_template false;
David J.
Yes, you are correct.
Thanks
Regards,
Amul Sul
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
No, the text is correct. When synchronous_commit=off there is a
possible delay between 'reported' transaction success and factual
saving on disk
Sent from my iPhone
> On 10 июля 2015 г., at 15:20, amul sul wrote:
>
> Hi,
>
>
> synchronous_commit description in document[1] :
> When off, there can
Hi,
synchronous_commit description in document[1] :
When off, there can be a delay between when success is reported to the client
and when the transaction is really guaranteed to be safe against a server
crash.
If I am not misunderstood, I guess it should be *When on* instead of *When
of
On 4/20/15 5:31 AM, Thom Brown wrote:
> On 20 April 2015 at 10:26, Amit Langote wrote:
>> Hi,
>>
>> s/inheiritance/inheritance/g
>
> Looks like it's misspelled in a few places:
>
> $ grep -r 'inheiritance' .
> ./src/test/regress/expected/updatable_views.out:-- security barrier
> view based on in
On 20 April 2015 at 10:26, Amit Langote wrote:
> Hi,
>
> s/inheiritance/inheritance/g
Looks like it's misspelled in a few places:
$ grep -r 'inheiritance' .
./src/test/regress/expected/updatable_views.out:-- security barrier
view based on inheiritance set
./src/test/regress/sql/updatable_views.s
Hi,
s/inheiritance/inheritance/g
Thanks,
Amit
typo-ddl-sgml.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Thu, Apr 9, 2015 at 3:23 AM, Amit Langote
wrote:
> Hi,
>
> Attached fixes a typo in mvcc.sgml
>
> - Read and explicit locking.on the master.
> + Read and explicit locking on the master.
>
Applied, thanks.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-
Hi,
Attached fixes a typo in mvcc.sgml
- Read and explicit locking.on the master.
+ Read and explicit locking on the master.
Thanks,
Amit
mvcc-doc-typo.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscriptio
On Wed, Dec 17, 2014 at 7:34 AM, David Johnston
wrote:
>
> The frontend must now take part in a Kerberos V5 authentication dialog
> (not described here, part of the Kerberos specification) with the server.
> If this is successful, the server responds with an AuthenticationOk,
> otherwise it respon
The frontend must now take part in a Kerberos V5 authentication dialog (not
described here, part of the Kerberos specification) with the server. If
this is successful, the server responds with an AuthenticationOk, otherwise
it responds with an ErrorResponse. This is no longer supported. This is not
On Sun, May 11, 2014 at 12:39 PM, Amit Langote wrote:
> Hi,
>
> Attached fixes a minor typo on test_shm_mq doc page
>
> s/"has been send"/"has been sent"
Applied. Thanks!
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscrip
Hi,
Attached fixes a minor typo on test_shm_mq doc page
s/"has been send"/"has been sent"
--
Amit
test-shm-mq-typo-fix.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On Wed, Apr 23, 2014 at 6:15 PM, Amit Langote wrote:
> Hi,
>
> Attached fixes a typo in doc/src/sgml/monitoring.sgml.
>
Sorry, typo in subject (kinda ironic!); I meant "s/trance/tranche?"
Patch attached again.
--
Amit
docs-monitoring-lwlock-tranche-not-trance-fix.patch
Description: Binary da
Hi,
Attached fixes a typo in doc/src/sgml/monitoring.sgml.
--
Amit
docs-monitoring-lwlock-tranche-not-trance-fix.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Wed, Nov 27, 2013 at 11:34 AM, Josh Kupershmidt wrote:
> Hi,
> It looks like a duplicated '>' character snuck into the 9.1.10 release
> notes, fix attached.
Thanks! Committed.
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your
Hi,
It looks like a duplicated '>' character snuck into the 9.1.10 release
notes, fix attached.
Josh
diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml
index 051ab69..20eff0b 100644
--- a/doc/src/sgml/release-9.1.sgml
+++ b/doc/src/sgml/release-9.1.sgml
@@ -268,7 +268,7 @@
Shigeru HANADA writes:
> I noticed a typo in the description of the column domains.collation_name.
>> Name of the collation of the column, null if default ...
> This view contains domain entries, so "Name of the collation of the
> domain" would be correct.
Committed, thanks!
I noticed a typo in the description of the column domains.collation_name.
> Name of the collation of the column, null if default ...
This view contains domain entries, so "Name of the collation of the
domain" would be correct.
--
Shigeru HANADA
diff --git a/doc/src/sgml/information_schema.sgml
Thom Brown writes:
> Attached is a patch to correct a typo on the dummy_seclabel page.
Applied, thanks!
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Hi,
Attached is a patch to correct a typo on the dummy_seclabel page. It
incorrectly gives the example:
shared_preload_libraries = 'dummy_label'
when it should be:
shared_preload_libraries = 'dummy_seclabel'
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user:
On Fri, Sep 9, 2011 at 9:34 AM, Shigehiro Honda
wrote:
> Hi,
>
> I noticed a typo in libpq.sgml. In the folowing partagrasoh, 'TCP_KEEPINTVL'
> should be 'TCP_KEEPCNT'. (In libpq's setKeepalivesCount(), '#ifdef
> TCP_KEEPCNT' is used.)
>
>
> keepalives_count
>
>
Hi,
I noticed a typo in libpq.sgml. In the folowing partagrasoh, 'TCP_KEEPINTVL'
should be 'TCP_KEEPCNT'. (In libpq's setKeepalivesCount(), '#ifdef TCP_KEEPCNT'
is used.)
keepalives_count
Controls the number of TCP keepalives that can be lost b
Erik Rijkers wrote:
> typo...
Applied, thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to y
typo...
ecpg.sgml.diff
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Thu, Feb 3, 2011 at 11:07, Thom Brown wrote:
> Someone submitted a comment to the docs (which I'll shortly delete)
> which points out a typo on the CREATE USER MAPPING page in the docs.
> A very brief patch is attached.
Thanks, applied.
--
Magnus Hagander
Me: http://www.hagander.net/
Work
Someone submitted a comment to the docs (which I'll shortly delete)
which points out a typo on the CREATE USER MAPPING page in the docs.
A very brief patch is attached.
They also added: "Also concerning this paragraph: a little more detail
on how exactly the two sources of encapsuled information a
Robert Haas wrote:
> On Thu, Jun 10, 2010 at 10:16 AM, Tom Lane wrote:
> > Robert Haas writes:
> >> On Thu, Jun 10, 2010 at 4:00 AM, Fujii Masao wrote:
> >>> The release note says "Allow continuous archive (WAL) files
> >>> to be streamed to a standby system" about SR. But no archive
> >>> files
On Sun, Jun 13, 2010 at 7:36 PM, Ian Barwick wrote:
> In "release-9.0.sgml" (sorry, can't provide patch right now), I suspect
> "is not substantially faster" should read "is now substantially faster"?
>
>
>
> As part of our decade-long effort to eliminate the pain of VACUUM,
> V
Hi
In "release-9.0.sgml" (sorry, can't provide patch right now), I suspect
"is not substantially faster" should read "is now substantially faster"?
As part of our decade-long effort to eliminate the pain of VACUUM,
VACUUM FULL is not substantially faster by
rewriting
On Thu, Jun 10, 2010 at 10:16 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Jun 10, 2010 at 4:00 AM, Fujii Masao wrote:
>>> The release note says "Allow continuous archive (WAL) files
>>> to be streamed to a standby system" about SR. But no archive
>>> files are streamed in SR. So we shou
Robert Haas writes:
> On Thu, Jun 10, 2010 at 4:00 AM, Fujii Masao wrote:
>> The release note says "Allow continuous archive (WAL) files
>> to be streamed to a standby system" about SR. But no archive
>> files are streamed in SR. So we should get rid of the word
>> "archive" from that sentence? H
On Thu, Jun 10, 2010 at 4:00 AM, Fujii Masao wrote:
> The release note says "Allow continuous archive (WAL) files
> to be streamed to a standby system" about SR. But no archive
> files are streamed in SR. So we should get rid of the word
> "archive" from that sentence? Here is the patch.
I don't
Hi,
The release note says "Allow continuous archive (WAL) files
to be streamed to a standby system" about SR. But no archive
files are streamed in SR. So we should get rid of the word
"archive" from that sentence? Here is the patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORA
Thanks, applied.
---
Erik Rijkers wrote:
> 'anyways' is not correct english, I think...
>
>
>
>
> --- doc/src/sgml/xtypes.sgml.orig 2010-04-06 02:48:33.0 +0200
> +++ doc/src/sgml/xtypes.sgml2010-04-06 0
On Tue, Apr 13, 2010 at 02:31, Fujii Masao wrote:
> Hi,
>
> I found the typo in config.sgml.
Applied, thanks.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscr
Hi,
I found the typo in config.sgml.
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 33d4e37..8d3c86b 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1733,7 +1733,7 @@ SET ENABLE_SEQSCAN TO OFF;
archive_mode is enabled, WAL archiving is tem
'anyways' is not correct english, I think...
--- doc/src/sgml/xtypes.sgml.orig 2010-04-06 02:48:33.0 +0200
+++ doc/src/sgml/xtypes.sgml2010-04-06 02:49:22.0 +0200
@@ -265,7 +265,7 @@
If the alignment is unimportant (either just for a specific function or
- beca
On Thu, Feb 25, 2010 at 10:57, Richard Huxton wrote:
> http://developer.postgresql.org/pgdocs/postgres/plperl-under-the-hood.html
>
> Contains several references to "plplerl" rather than "plperl".
Thanks, fixed.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.
http://developer.postgresql.org/pgdocs/postgres/plperl-under-the-hood.html
Contains several references to "plplerl" rather than "plperl".
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresq
Erik Rijkers wrote:
> --- doc/src/sgml/ref/psql-ref.sgml.orig 2009-02-09 01:32:54.0 +0100
> +++ doc/src/sgml/ref/psql-ref.sgml 2009-02-09 01:33:44.0 +0100
> @@ -1746,7 +1746,7 @@
>You can specify an optional second argument, if it is provided it
>may be
--- doc/src/sgml/ref/psql-ref.sgml.orig 2009-02-09 01:32:54.0 +0100
+++ doc/src/sgml/ref/psql-ref.sgml 2009-02-09 01:33:44.0 +0100
@@ -1746,7 +1746,7 @@
You can specify an optional second argument, if it is provided it
may be either on or off
wh
Patch applied. Thanks. Your documentation changes can be viewed in
five minutes using links on the developer's page,
http://www.postgresql.org/developer/testing.
---
Devrim GUNDUZ wrote:
>
> Hi,
>
> The attached files
Hi,
The attached files fix the typos in 8.1/runtime.sgml and
HEAD/config.sgml, per Jeroen Vermeulen.
Regards,
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Au
Done.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Bruce Momjian
Sent: Thu 10/13/2005 10:08 PM
To: Alvaro Herrera
Cc: pgsql-docs@postgresql.org; [EMAIL PROTECTED]; Marc G. Fournier
Subject: Re: [pgsql-www] [DOCS] Typo in README.dist-split
For clarity, the last line should
For clarity, the last line should be:
different, incompatible split where all subpackages were required.)
---
Alvaro Herrera wrote:
> On Fri, Sep 23, 2005 at 02:02:47PM -0400, Bruce Momjian wrote:
> >
> > This need
This is still not fixed!
---
Alvaro Herrera wrote:
> On Fri, Sep 23, 2005 at 02:02:47PM -0400, Bruce Momjian wrote:
> >
> > This needs to be fixed. I still see the incorrect file contents
> > outlined below.
>
> In fact,
On Fri, Sep 23, 2005 at 02:02:47PM -0400, Bruce Momjian wrote:
>
> This needs to be fixed. I still see the incorrect file contents
> outlined below.
In fact, I see the _wrong_ "where" was fixed! So they now are both
wrong :-)
> --
This needs to be fixed. I still see the incorrect file contents
outlined below.
---
Alvaro Herrera wrote:
> Not sure what mailing list should I be sending this report to. Anyway,
> the problem is in the README.dist-split f
Actually, that wouldn't fix it ... but, I've fixed commit messages for
both you and Andrew now ...
On Sun, 4 Sep 2005, Alvaro Herrera wrote:
On Sun, Sep 04, 2005 at 08:06:38PM -0400, Tom Lane wrote:
I wrote:
Was Alvaro's commit the only one over the weekend?
I pulled down the CVS logs
On Sun, Sep 04, 2005 at 08:06:38PM -0400, Tom Lane wrote:
> I wrote:
> > Was Alvaro's commit the only one over the weekend?
>
> I pulled down the CVS logs and verified that it was the only such
> commit. So the problem is most likely specific to Alvaro's account
> and not a list-wide issue.
Yeah
I wrote:
> Was Alvaro's commit the only one over the weekend?
I pulled down the CVS logs and verified that it was the only such
commit. So the problem is most likely specific to Alvaro's account
and not a list-wide issue.
regards, tom lane
---(end
It is possible I did not see it. I now remember I saw the CVS log
message, not the email text.
---
Tom Lane wrote:
> Bruce Momjian writes:
> > Alvaro Herrera wrote:
> >> Hmm, I just committed the fix and was waiting to rec
Bruce Momjian writes:
> Alvaro Herrera wrote:
>> Hmm, I just committed the fix and was waiting to receive the
>> pgsql-committers message before sending the confirmation, but I haven't
>> gotten it yet. Did I do something wrong? It was my first commit to
>> this repo.
>>
>> ... maybe I should s
I did see the commit message. Perhaps it will show in the archives
tomorrow:
http://archives.postgresql.org/pgsql-committers/2005-09/index.php
---
Alvaro Herrera wrote:
> On Sun, Sep 04, 2005 at 09:52:49AM -0400, B
On Sun, Sep 04, 2005 at 09:52:49AM -0400, Bruce Momjian wrote:
> Richard van den Berg wrote:
> > The release notes for PostgreSQL 8.1 read:
> >
> > ---
> > E.1.3.12. pg_dump Changes
> >
> > * Add -n / --schema switch to pg_restore (Richard v
Fixed, thanks.
---
Richard van den Berg wrote:
> The release notes for PostgreSQL 8.1 read:
>
> ---
> E.1.3.12. pg_dump Changes
>
> * Add -n / --schema switch to pg_r
The release notes for PostgreSQL 8.1 read:
---
E.1.3.12. pg_dump Changes
* Add -n / --schema switch to pg_restore (Richard van den Bergg)
---
There is one g too many in my last name. It wo
Not sure what mailing list should I be sending this report to. Anyway,
the problem is in the README.dist-split file to be found in some
version's directories -- I'm looking at
ftp://ftp.cl.postgresql.org/ftp/pub/postgresql/source/v8.1beta/README.dist-split
The last paragraph states
"Previous
The line is now:
administrator to make sure that data is guaranteed to be written to permanent
so it seems we are OK.
---
Thomas F. O'Connell wrote:
> I hope it was fixed to "Guaranteed" rather than "Guarenteed"... ;)
>
I hope it was fixed to "Guaranteed" rather than "Guarenteed"... ;)
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On Apr 1, 2005, at 10:42 PM, Bruce Momjian wrote:
Fixed. Thank
Fixed. Thanks.
---
Bruno Wolff III wrote:
> "Guarenteed" is mispelled as "guarantted" in the 8.0.2 release notes (in
> the "Enable the wal_sync_method" bullet point).
>
> ---(end of broadcast)---
"Guarenteed" is mispelled as "guarantted" in the 8.0.2 release notes (in
the "Enable the wal_sync_method" bullet point).
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Wed, Feb 02, 2005 at 11:15:10PM -0700, Michael Fuhr wrote:
>
> Here's a brief article about how the "y" in "ye" is a misspelling
> of the "thorn" (þ) character:
>
> http://www.bartleby.com/68/15/6615.html
Here's another article mentioning that "y" was used in place of
thorn on printing presses
On Tue, Feb 01, 2005 at 10:33:43AM -0800, Hashem Masoud wrote:
> I believe this is a typo in the file
> performance-tips.html (perform.sgml):
>
> This plan proposes to extract the 50 interesting rows
> of tenk1 using ye same olde index scan, stash them
> into an in-memory hash table,
What's the
Hi all,
I believe this is a typo in the file
performance-tips.html (perform.sgml):
This plan proposes to extract the 50 interesting rows
of tenk1 using ye same olde index scan, stash them
into an in-memory hash table,
Regards,
Hashem Masoud
_
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> In "E.1.2. Migration to version 8.0" the folowing paragraph appears to use
> "one less than the current year" when it should be "one less than the correct
> year" based on later comments about that fix.
Yeah, I think you're right. Change made.
In "E.1.2. Migration to version 8.0" the folowing paragraph appears to use
"one less than the current year" when it should be "one less than the correct
year" based on later comments about that fix.
The extract() function (also called date_part) now returns the proper year for
BC dates. It previou
Am Donnerstag, 22. April 2004 05:14 schrieb Alvis Tunkelis:
> Table 30-38. view_table_usage Columns
>
> 'Description' for table_catalog should be corrected:
> Name of the database that contains the table the table that is used by the
> view (always the current database) ^^^
Fixed, thanks.
Table 30-38. view_table_usage Columns
'Description' for table_catalog should be
corrected:
Name of the database that contains the table the
table that is used by the view (always the current database)
^^^
Regar
93 matches
Mail list logo
