I just got this crazy, stupid or maybe genius idea :-)
One thing that I've learned in this thread is that fat indexes (i.e.
some index on some_table(a,b,c,d,e,f)) is to be avoided as much as
possible.
One of our biggest indexes looks like this:
acc_trans(customer_id, trans_type, created)
For th
On Tue, Sep 28, 2010 at 3:14 PM, Guy Rouillier wrote:
> On 9/28/2010 4:45 PM, Greg Smith wrote:
>>
>> Tory M Blue wrote:
>>>
>>> I'm doing an OS upgrade and have been sitting on 8.4.3 for sometime. I
>>> was wondering if it's better for the short term just to bring things
>>> to 8.4.4 and let 9.0
On 9/28/2010 4:45 PM, Greg Smith wrote:
Tory M Blue wrote:
I'm doing an OS upgrade and have been sitting on 8.4.3 for sometime. I
was wondering if it's better for the short term just to bring things
to 8.4.4 and let 9.0 bake a bit longer, or are people with large data
sets running 9.0 in product
Tory M Blue wrote:
I'm doing an OS upgrade and have been sitting on 8.4.3 for sometime. I
was wondering if it's better for the short term just to bring things
to 8.4.4 and let 9.0 bake a bit longer, or are people with large data
sets running 9.0 in production already?
I'm aware of two people
Tory,
We will continue to test under 9.0 but will keep production at 8.4.4 for a
while longer as we want to see what kinds of issues show up over the next
few weeks with 9.0. 9.0 has some features we would like to use but it isn't
worth the risk of production. I think that the PostGres team has o
I'm doing an OS upgrade and have been sitting on 8.4.3 for sometime. I
was wondering if it's better for the short term just to bring things
to 8.4.4 and let 9.0 bake a bit longer, or are people with large data
sets running 9.0 in production already?
Just looking for 9.0 feedback (understand it's s
On Wed, Sep 22, 2010 at 9:36 AM, Ogden wrote:
>
> On Sep 21, 2010, at 2:34 PM, Ogden wrote:
>
>>
>> On Sep 21, 2010, at 2:16 PM, Greg Smith wrote:
>>
>>> Joshua D. Drake wrote:
PostgreSQL's defaults are based on extremely small and some would say
(non production) size databases. As a mat
On Tue, September 28, 2010 12:01, Nimesh Satam wrote:
> Hi,
>
> Can any one of you suggest how the archived Xlogs can be cleaned in
> postgres-9.
>
> We want to use streaming replication and have set the "wal_level" to
> "hot_standby" and "archive_mode" to "on".
>
See contrib/pg_archivecleanup:
h
Hi,
Can any one of you suggest how the archived Xlogs can be cleaned in
postgres-9.
We want to use streaming replication and have set the "wal_level" to
"hot_standby" and "archive_mode" to "on".
Regards,
Nimesh.
On 27/09/10 08:06, adrian.kitching...@dse.vic.gov.au wrote:
>
> /2010-09-27 09:53:19 EST LOG: server process (PID 2564) was terminated
> by exception 0xC005/
> /2010-09-27 09:53:19 EST HINT: See C include file "ntstatus.h" for a
> description of the hexadecimal value./
That's an access viol
10 matches
Mail list logo
