On Mon, Mar 27, 2006 at 10:20:23AM +, JP Glutting wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2360
> Logged by: JP Glutting
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1 (8.0)
> Operating system: Windows XP SP2
> Description:
The following bug has been logged online:
Bug reference: 2360
Logged by: JP Glutting
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1 (8.0)
Operating system: Windows XP SP2
Description:Backup produces "ERROR: could not convert UTF8 character
to ISO8859-1"
Deta
On Mon, Mar 27, 2006 at 09:50:38AM -0500, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Sun, Mar 26, 2006 at 08:34:46PM -0500, Tom Lane wrote:
> >> The question is whether doing either one is really a material
> >> improvement, seeing that neither is going to provoke an abort
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Sun, Mar 26, 2006 at 08:34:46PM -0500, Tom Lane wrote:
>> The question is whether doing either one is really a material
>> improvement, seeing that neither is going to provoke an abort
>> until/unless the backend actually tries to write something to t
The following bug has been logged online:
Bug reference: 2362
Logged by: Tomasz Ostrowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: not applicable
Operating system: not applicable
Description:bug reporting form: "submit" shows only "&id=[number]"
Details:
The following bug has been logged online:
Bug reference: 2361
Logged by: Tomasz Ostrowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows XP
Description:windows installer: pg_config not installed when
"Database Server" not chosen
D
On Sun, Mar 26, 2006 at 08:34:46PM -0500, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Allowing SIGPIPE to kill the backend is completely infeasible, as the
> >> backend would be unable to release locks etc before dying.
>
> > So the upshot is really not
It sounds like you probably ran for a long time (or more accurately did
a large number of updates/deletes) without vacuuming. Due to the way
vacuum works, this would result in a very large amount of wasted space.
While you could VACUUM FULL and REINDEX to fix this, in your case you'd
probably be b