On Thu, Oct 12, 2017 at 12:13 PM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/bug-reporting.html
> Description:
>
> on https://www.postgresql.org/download/linux/redhat/
> for optional initialize it says:
> /usr/p
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/bug-reporting.html
Description:
on https://www.postgresql.org/download/linux/redhat/
for optional initialize it says:
/usr/pgsql-10/bin/postgresql10-setup initdb
That file does not
michaelr...@gmail.com writes:
> In this example:
> > Here is a more complex example:
> to_timestamp('15:12:02.020.001230',
> 'HH:MI:SS.MS.US') is 15 hours, 12 minutes, and 2 seconds + 20
> milliseconds +
> 1230 microseconds = 2.021230 seconds.
> HH needs to be HH24
You're right, thanks for rep
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/functions-formatting.html
Description:
In this example:
> Here is a more complex example: to_timestamp('15:12:02.020.001230',
'HH:MI:SS.MS.US') is 15 hours, 12 minutes, and 2 seco
On Sun, Dec 25, 2016 at 11:42 PM, wrote:
> I just installed version 9.6.1 on RHEL 6.5 x64. I used the installed from
> your documentation page.
> I tried to start the database and got:
>
> postgres -D /opt/PostgreSQL/9.6/data
> FATAL: unrecognized configuration parameter
> "dynamic_shared_memor
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/server-start.html
Description:
I just installed version 9.6.1 on RHEL 6.5 x64. I used the installed from
your documentation page.
I tried to start the database and got:
postgres
Hi Marcin,
The version of the repo files != the version of PostgreSQL packages.
pgdg-fedora or pgdg-redhat (or whatever) are the repo packages, and they carry
only the major number: 9.5. The rest is the build number for that specific
package.
So, there is nothing incorrect there.
Please email
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/release-9-5-3.html
Description:
Hi team,
Location
https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-6-x86_64/
should contain repo for 9.5-3, but for some reason it doe
Le 2 mai 2016 3:39 AM, "Peter Eisentraut"
a écrit :
>
> On 05/01/2016 11:18 AM, Guillaume Lelarge wrote:
> > While updating the translation to the latest minor releases, I found
> > this in xindex.sgml:
> >
> >
> > GIN Support Functions
> >
> > Shouldn't this be "BRIN Support Functions"?
>
Hi,
While updating the translation to the latest minor releases, I found this
in xindex.sgml:
GIN Support Functions
Shouldn't this be "BRIN Support Functions"?
Patch attached (for 9.5 and master).
Regards.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
di
The Notes section of the ALTER TABLE reference page explains that ALTER
DROP COLUMN doesn't immediately reclaim any space, and then says:
To force an immediate rewrite of the table, you can use VACUUM FULL,
CLUSTER or one of the forms of ALTER TABLE that forces a rewrite. This
results
Em 19-05-2011 18:04, Peter Eisentraut escreveu:
I think we should just remove the second column from the table and
rephrase the paragraph above it accordingly. At some point in the
future we could introduce a separate optional data field that adds
actual additional information about the error co
Ref: http://developer.postgresql.org/pgdocs/postgres/errcodes-appendix.html
It seems to me that the second and the third column in that table are
redundant. The third is just the second with underscores and lower-case
letters. I find this pretty confusing, first because of the sheer
(apparent) v
On Sat, May 7, 2011 at 20:03, Khusro Jaleel
wrote:
> On 07/05/11 18:46, Magnus Hagander wrote:
>
>> clientcert=1 makes the server request a client certificate - but does
>> not use it for authentication. So the client just has to present *any
>> valid* client certificate, and can then use whatever
On 07/05/11 18:46, Magnus Hagander wrote:
clientcert=1 makes the server request a client certificate - but does
not use it for authentication. So the client just has to present *any
valid* client certificate, and can then use whatever other
authenticaiton method is specified (md5, ldap, etc).
On Sat, May 7, 2011 at 18:40, Khusro Jaleel
wrote:
> Hello, according to section 17.8.1 of the docs, I have added "clientcert" to
> a hostssl line in my pg_hba.conf file, but upon restart of the server, I'm
> getting the following error and the server fails to start up:
>
> LOG: invalid authentic
Hello, according to section 17.8.1 of the docs, I have added
"clientcert" to a hostssl line in my pg_hba.conf file, but upon restart
of the server, I'm getting the following error and the server fails to
start up:
LOG: invalid authentication method "clientcert"
CONTEXT: line 82 of configurat
On Wed, Jul 21, 2010 at 1:07 PM, Kevin Grittner
wrote:
> Marc Cousin wrote:
>
>> DECLARE
>> CURSOR referrer_keys IS
>
>> I guess it should be
>>
>> DECLARE
>> referrer_keys CURSOR IS
>
>> If I'm right, a patch is attached (the code works with the
>> correction)
>
> The patch looks correct
Marc Cousin wrote:
> DECLARE
> CURSOR referrer_keys IS
> I guess it should be
>
> DECLARE
> referrer_keys CURSOR IS
> If I'm right, a patch is attached (the code works with the
> correction)
The patch looks correct to me.
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@
Hi,
A user had a syntax problem with a cursor declaration. After a bit of digging,
the code he used came directly from the documentation :
DECLARE
CURSOR referrer_keys IS
SELECT * FROM cs_referrer_keys
ORDER BY try_order;
func_body text;
func_cmd text;
I guess it sho
My reasoning was :
Look to every query on a time line
savepoint 1
query 1
savepoint j
query j
.
savepoint n
query n
When I release savepoint j , I think 'everythin before savepoint j is ok and
safe', and so I don't need the savepoints before savepoint j anymore (cause
they're save) when
On Sep 24, 2007, at 10:03 , Michael Cochez wrote:
In http://www.postgresql.org/docs/8.2/static/tutorial-
transactions.html
"After rolling back to a savepoint, it continues to be defined, so
you can roll back to it several times. Conversely, if you are sure
you won't need to roll back to a p
In http://www.postgresql.org/docs/8.2/static/tutorial-transactions.html
"After rolling back to a savepoint, it continues to be defined, so you can roll
back to it several times. Conversely, if you are sure you won't need to roll
back to a particular savepoint again, it can be released, so the sys
Dosya eki: document.zip
Bu postaya eklenmis bir dosya, viruslu oldugu icin silindi.
Result: Virus Detected
Virus Name: [EMAIL PROTECTED]
File Attachment: document.zip
Attachment Status: deleted
---(end of broadcast)---
TIP 2: you can get off
Hi. I have just learned how to create my own triggers on plpgsql
language, and I think I have discover an error into the doc:
http://www.postgresql.org/docs/current/static/plpgsql-statements.html#PLPGSQL-SELECT-INTO
DECLARE
users_rec RECORD;
full_name varchar;
BEGIN
SELECT INT
Hi. I have just learned how to create my own triggers on plpgsql
language, and I think I have discover an error into the doc:
http://www.postgresql.org/docs/current/static/plpgsql-statements.html#PLPGSQL-SELECT-INTO
DECLARE
Folks,
Am I missing something here? We're preparing for migration, but I can't find
anywhere a centralized list of the new error messages. Is it in the source
somewhere? If so, can we add it to the documentation?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
-
Josh Berkus <[EMAIL PROTECTED]> writes:
> Am I missing something here? We're preparing for migration, but I
> can't find anywhere a centralized list of the new error messages. Is
> it in the source somewhere? If so, can we add it to the
> documentation?
You could make one by running gettext ---
Tom,
> Or were you looking for src/include/utils/errcodes.h ?
More or less.
The issue is that many projects have internal code to handle PG error messages
by parsing them for certain text. The overhaul of message handling is going
to break that code; users need to know what the new messages
The issue is that many projects have internal code to handle PG error
messages
by parsing them for certain text. The overhaul of message handling
is going
to break that code; users need to know what the new messages and/or
codes are
before migrating.
I concur, I have such an application and it
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Or were you looking for src/include/utils/errcodes.h ?
> I think we should put such a list in the documentation, at least for those
> error codes that we have really assigned.
I have no objection to that. I have doubts about the
The point of including the message texts is
for people supporting various versions who
are looking directly at the message texts
for earlier versions.
This also allows them to upgrade the error
handling to use the new error codes instead
of relying on the message text (which is what
we want).
ele
The issue is that many projects have internal code to handle PG error
messages
by parsing them for certain text. The overhaul of message handling
is going
to break that code; users need to know what the new messages and/or
codes are
before migrating.
I concur, I have such an application and it
Tom Lane writes:
> Or were you looking for src/include/utils/errcodes.h ?
I think we should put such a list in the documentation, at least for those
error codes that we have really assigned.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)--
34 matches
Mail list logo
