Alan Martin wrote:
The following bug has been logged online:
Bug reference: 5204
Logged by: Alan Martin
Email address: alan.mar...@mightyautoparts.com
PostgreSQL version: 08.04.0100
Operating system: Windows 7 64-bit
Description:ODBC connection NOT working
Details:
Michael Genereux writes:
> MacOS X 10.5.8
Oh, that's because of ossp-uuid's hopelessly broken approach to
dealing with conflicts with system-provided definitions of uuid_t.
There's not much we can do about it. You could try filing a bug
with them if you care. It's mostly cosmetic though --- at
Michael Genereux writes:
> configure: WARNING: ossp/uuid.h: present but cannot be compiled
Hmm, exactly what version of ossp-uuid are you using, and on what
platform? Also, which PG version is this?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
configure: WARNING: ossp/uuid.h: present but cannot be compiled
configure: WARNING: ossp/uuid.h: check for missing prerequisite headers?
configure: WARNING: ossp/uuid.h: see the Autoconf documentation
configure: WARNING: ossp/uuid.h: section "Present But Cannot Be
Compiled"
configure: WARNI
Sorry force of habit with the CC.
Sorry a bit of confusion here with the documentations meaing.
Does the autovacuum_naptime also then mean that the daemon will wil try to scan
all databases within system in the autovacuum_naptime?
Therefore as the number of databases increases the amount of work
(Please keep the list CC'd so that others can help)
Autovacuum_naptime is the minimum delay between autovacuum runs *on any
given database*, so what you're seeing is normal.
A.J.Masterton wrote:
> The relevant lines from the config file are below. In this exmple the
> autovacuum_naptime is set t
The following bug has been logged online:
Bug reference: 5207
Logged by: denny saviant
Email address: konohabluefl...@gmail.com
PostgreSQL version: 8.4.1
Operating system: windows xp pro sp3
Description:unable to start postgresql server services
Details:
I installed
