The following bug has been logged online:
Bug reference: 3802
Logged by: Craig
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: windows vista
Description:cant install
Details:
Have tried to install the programme via the executable
On Thu, Dec 06, 2007 at 12:21:38PM +, Craig wrote:
The following bug has been logged online:
Bug reference: 3802
Logged by: Craig
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: windows vista
Description:cant install
Details:
The following bug has been logged online:
Bug reference: 3804
Logged by: Juergen Zimmermann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3 beta4
Operating system: Windows XP Prof. SP2
Description:initdb.exe cannot be started
Details:
I wanted to install
The following bug has been logged online:
Bug reference: 3803
Logged by: srinath
Email address: [EMAIL PROTECTED]
PostgreSQL version: PostgreSQL 8.1
Operating system: Linux
Description:Error while sending request to database
Details:
hi,
when i connecting my
Tom Lane escribió:
Alvaro Herrera [EMAIL PROTECTED] writes:
I don't advocate changing that ERROR to anything else. The message
wording, as Tom says, can easily be changed -- I think this patch should
be enough. Feel free to propose better wording.
Minor gripe: all three variants of the
On Thu, 2007-12-06 at 11:33 -0300, Alvaro Herrera wrote:
Tom Lane escribió:
Alvaro Herrera [EMAIL PROTECTED] writes:
I don't advocate changing that ERROR to anything else. The message
wording, as Tom says, can easily be changed -- I think this patch should
be enough. Feel free to
Simon Riggs escribió:
Sorry to come in on late on this: That wording is better, but it still
doesn't explain why it has occurred or what the user should do about it.
I think we will get other complaints saying why has my autovacuum been
canceled? and what should I do about this?.
Perhaps
On Thu, 2007-12-06 at 12:03 -0300, Alvaro Herrera wrote:
Simon Riggs escribió:
Sorry to come in on late on this: That wording is better, but it still
doesn't explain why it has occurred or what the user should do about it.
I think we will get other complaints saying why has my autovacuum
Simon Riggs [EMAIL PROTECTED] writes:
True. We can say task will be automatically re-scheduled, so that
people understand the message and don't start asking us.
How about temporarily canceling autovacuum task? This is accurate
regardless of the origin of the SIGINT.
Tom Lane escribió:
Simon Riggs [EMAIL PROTECTED] writes:
True. We can say task will be automatically re-scheduled, so that
people understand the message and don't start asking us.
How about temporarily canceling autovacuum task? This is accurate
regardless of the origin of the SIGINT.
depesz [EMAIL PROTECTED] writes:
Description:csvlog skips some logs
The point here is that CSV-format log output doesn't include the
DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
you might get with normal output.
I suppose this was intentional in order to keep the CSV
On Thu, 2007-12-06 at 12:24 -0300, Alvaro Herrera wrote:
Tom Lane escribió:
Simon Riggs [EMAIL PROTECTED] writes:
True. We can say task will be automatically re-scheduled, so that
people understand the message and don't start asking us.
How about temporarily canceling autovacuum
Tom Lane wrote:
depesz [EMAIL PROTECTED] writes:
Description:csvlog skips some logs
The point here is that CSV-format log output doesn't include the
DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
you might get with normal output.
I suppose this was intentional in
Andrew Dunstan [EMAIL PROTECTED] writes:
I can't see any very good reason for text logs to have different
content from CSV logs.
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add six
Tom Lane wrote:
depesz [EMAIL PROTECTED] writes:
Description:csvlog skips some logs
The point here is that CSV-format log output doesn't include the
DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
you might get with normal output.
I suppose this was
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
I can't see any very good reason for text logs to have different
content from CSV logs.
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
On Thu, Dec 06, 2007 at 12:34:55PM +, srinath wrote:
when i connecting my postgresql which giving
org.postgresql.util.PSQLException: ERROR: conversion between UNICODE and
MULE_INTERNAL is not supported.please send solution about this problem.
Sounds like you have your application
The following bug has been logged online:
Bug reference: 3806
Logged by: Ted Wen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta3
Operating system: Windows
Description:PreparedStatement.setString(String) throws exception
Details:
Code fragment:
String
The following bug has been logged online:
Bug reference: 3807
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0 beta4
Operating system: WindowsXP
Description:SQL : select like statement
Details:
Why? specific change?
statement: select * from
Kris-
Thanks for digging into the code for that. Unfortunately, I'm now more
confused.
the actual default at initdb time can be set as high as nbuffers *
50,
where the max shared_buffers is 4096. So the default max_fsm_pages
for a
beefier machine will be 204800 which is what you will
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add six more text fields to the CSV format
either. Thoughts?
Really? Six? In
On Thu, 6 Dec 2007, Reece Hart wrote:
This seems to directly say that the commented out settings are the
default values, and furthermore that one must restart to get the
indicated default back. Based on your evidence, it seems that the
postgresql.conf comment for max_fsm_pages needs revising
22 matches
Mail list logo
