On 14/09/12 06:11, Ross Reedstrom wrote:
Hey PostgreSQL speed demons -
At work, we're considering an AppScale deployment (that's the Google App Engine
roll-your-own http://appscale.cs.ucsb.edu/). It supports multiple technologies
to back the datastore part of the platform (HBase, Hypertable, MySQ
On Wed, Apr 18, 2012 at 05:09:29PM -0700, Josh Berkus wrote:
> On 4/12/12 8:47 AM, Steve Crawford wrote:
> > On 03/30/2012 05:51 PM, Josh Berkus wrote:
> >>
> >> So this turned out to be a Linux kernel issue. Will document it on
> >> www.databasesoup.com.
> > Anytime soon? About to build two Post
Regards, Ross.
Dimitri Fontaine gave a excellent talk in the last PgCon about the
migration of Fotolog from MySQL to
PostgreSQL with amazing advices around this, so you can contact him for
his advice.
On 09/13/2012 02:11 PM, Ross Reedstrom wrote:
Hey PostgreSQL speed demons -
At work, we're c
Hey PostgreSQL speed demons -
At work, we're considering an AppScale deployment (that's the Google App Engine
roll-your-own http://appscale.cs.ucsb.edu/). It supports multiple technologies
to back the datastore part of the platform (HBase, Hypertable, MySQL Cluster,
Cassandra, Voldemort, MongoDB, M
Bill Martin writes:
> Tom Lane writes:
>> He can do it without having to change his schema --- but it's the index
>> column, not the underlying content column, that needs its statistics
>> target adjusted.
> How can I adjust the statistics target of the index?
Just pretend it's a table.
> Tom Lane writes:
> He can do it without having to change his schema --- but it's the index
> column, not the underlying content column, that needs its statistics
> target adjusted.
> regards, tom lane
How can I adjust the statistics target of the index?
--
Sent via p
Jesper Krogh writes:
> On 13/09/12 16:42, Bill Martin wrote:
>> Yes, I've run the ANALYZE command. Regards, Bill Martin
> The main problem in your case is actually that you dont store the
> tsvector in the table.
Oh, duh, obviously I lack caffeine this morning.
> If you store to_tsvector('sim
On 13/09/12 16:42, Bill Martin wrote:
Yes, I've run the ANALYZE command. Regards, Bill Martin
The main problem in your case is actually that you dont store the
tsvector in the table.
If you store to_tsvector('simple',content.content) in a column in
the database and search against that instead
> Tom Lane writes:
>> Bill Martin writes:
>> I've tried different values for the statistics but it is all the same (the
>> planner decide to switch to a seqscan if the limit is 10).
>> ALTER TABLE core_content ALTER column content SET STATISTICS 1000;
> Um, did you actually do an ANALYZE after
Bill Martin writes:
> I´ve tried different values for the statistics but it is all the same (the
> planner decide to switch to a seqscan if the limit is 10).
> ALTER TABLE core_content ALTER column content SET STATISTICS 1000;
Um, did you actually do an ANALYZE after changing that?
Dne 13.09.2012 11:22, Venkat Balaji napsal:
On Wed, Sep 12, 2012 at 7:42 PM, Scott Marlowe
wrote:
On Wed, Sep 12, 2012 at 12:57 AM, Venkat Balaji
wrote:
> We are using PostgreSQL-9.0.1.
You are missing almost 2 years of updates, bug fixes, and security
fixes.
Thank you Scott, We are plann
On Wed, Sep 12, 2012 at 7:42 PM, Scott Marlowe wrote:
> On Wed, Sep 12, 2012 at 12:57 AM, Venkat Balaji
> wrote:
>
> > We are using PostgreSQL-9.0.1.
>
> You are missing almost 2 years of updates, bug fixes, and security fixes.
>
Thank you Scott, We are planning to upgrade to the latest version
Tom Lane writes:
> Bill Martin writes:
>> I´ve created following table which contains one million records.
>> ...
>> "Limit (cost=10091.09..19305.68 rows=3927 width=621) (actual
>> time=0.255..0.255 rows=0 loops=1)"
>> " -> Bitmap Heap Scan on core_content content (cost=10091.09..57046.32
13 matches
Mail list logo
