On Mon, Sep 27, 2010 at 8:50 PM, Dave Crooke wrote:
>
> Our Java application manages its own schema. Some of this is from
> Hibernate, but some is hand-crafted JDBC.
>
> By way of an upgrade path, we have a few places where we have added
> additional indexes to optimize performance, and so at sta
Our Java application manages its own schema. Some of this is from Hibernate,
but some is hand-crafted JDBC.
By way of an upgrade path, we have a few places where we have added
additional indexes to optimize performance, and so at startup time the
application issues "CREATE INDEX ..." statements fo
On Thu, Sep 23, 2010 at 10:26 AM, Dmitry Teslenko wrote:
> I know I can set enable_seqscan = off.
> Is there other ways to enforce index usage?
Not really, but I suspect random_page_cost and seq_page_cost might
help the planner make better decisions. Is your data by any chance
mostly cached in m
Last bit of promotion here for this project:
http://github.com/gregs1104/stream-scaling has been updated with a few
more results anonymously submitted by list members here. The updated
chart really fleshes out how the RAM scaling works on the older
multi-socket AMD servers now. That's someth
Hi again Thom
Just a quick update regarding my previous reply to you. I managed to do a
deeper uninstall of Postgresql 8.3 with these following steps.
* Remove the Registry entries.
(HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-8.3) and
(HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQ
Hi Thom
Thanks for the reply and the log seems to have shed some light. Looks like
I have my old postgres 8.3 service still running concurrently which is
interfering with the new 9.0 service. This is the message that comes up a
lot in the log.
2010-09-24 15:39:34 EST LOG: unexpected EOF on cl
