Brian Connolly writes:
> Any help that you can provide would be greatly appreciated.
I'd suggest trying to get rid of the weird little subselects, like this
one:
> ... SELECT * FROM assayresult."c69d129_particle_size_result_fields"
> WHERE (((SELECT Container FROM exp.Data WHERE RowId = DataId
Hey Brian,
Brian Connolly wrote:
> (I had to send a follow up email due the length of email restrictions on the
> mailing list.)
A tip for when you have this problem in the future -- turn off html mail.
It will reduce your email message length by 50% - 90%.
HTH
Bosco.
--
Sent via pgsql-perfor
Here is the explain analyze output for when enable_material is 'off' and
information on the postgresql version, settings and server configuration (I
had to send a follow up email due the length of email restrictions on the
mailing list.)
(I apologize for the length of these email messages. And if
Didik Prasetyo wrote:
> I had a problem with performance engine database, I use the server
> with the following specifications
>
> 1. its storage configuration?
>Storage SCSI 15K RAID 5
> 2. how his network?
> 2 gigabit bonding.
> 3. type / behavior of applications that connect
On Sat, Apr 30, 2011 at 4:51 AM, Hsien-Wen Chu wrote:
> since the block size is 8k for the default, and it consisted with many
> tuple/line; as my understand, if any tuple/line is changed(maybe
> update, insert, delete). the block will be marked as dirty block. and
> then it will be flashed to dis
We have a generated query from our web application which takes far longer to
complete in 9.0.4, than in 8.3.7 (>60sec in 9.0.4 ~10sec in 8.3.7)
The query plan generated in 9.0, includes a Materialize step which takes the
bulk of the time for the query. If I disable materialize (by running set
ena
Rishabh Kumar Jain wrote:
> I am getting data from 10 tables in a view.
> I don't know on which pair of tables I have to add explicit joins
> to improve performance.
There's usually some fairly natural order in terms of understanding
the request. I find it's often good to try to state in word
On Thu, May 5, 2011 at 1:02 AM, Josh Berkus wrote:
>
>> FWIW, EnterpriseDB's "InfiniCache" provides the same caching benefit. The
>> way that works is when PG goes to evict a page from shared buffers that page
>> gets compressed and stuffed into a memcache cluster. When PG determines that
>> a
I did the hot standby configured earlier and at that time I started
using(querying) the standby database.
May be something missed on the archive command.
On Wed, May 4, 2011 at 8:44 PM, Josh Berkus wrote:
>
> > While doing so I got the "*Query failed ERROR: catalog is missing 1
> > attribute(s