http://vipglobalcp.com/ekroe/dzbyvvuhprtdsjcruzrsjnkfrxiad.php
Ioana Danes
11/1/2013 4:50:50 PM
Hello,
I have a question regarding the maintenance_work_mem and the index creation.
I have a dedicated postgresql server with 16GB of RAM.
The shared_buffers is 4GB and the maintenance_work_mem is 2GB.
I have a table with 28 mil records and 2 one-column indexes:
1. First index is for an inte
Hi everyone,
I am running a test with 1 thread calling a stored
procedure in an endless loop. The stored procedure
inserts 1000 records in a table that does not have
indexes or constraints.
In the log file I see that the time to execute the
procedure sometimes it jumps from 100 ms to 700 ms.
The a
transid from someunionview order by transid
desc limit 1;
Thank you for your time,
Ioana Danes
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Jeff Davis <[EMAIL PROTECTED]> writes:
> > If PostgreSQL could sort the result of a union by
> merging the results of
> > two index sc
Hi,
I tried and this does does not work either.
Thank you,
Ioana
--- "Jim C. Nasby" <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 18, 2006 at 03:32:15PM -0700, Jeff Davis
> wrote:
> > On Wed, 2006-10-18 at 17:10 -0500, Jim C. Nasby
> wrote:
> > > Sorry, don't have the earlier part of this
> thread, bu
,
Ioana Danes
> constraint exclusion and inheritance won't help him.
>
> The problem is that he has two indexes, and he needs
> to find the max
> between both of them. PostgreSQL isn't smart enough
> to recognize that it
> can use two indexes, find the max in each o
Hello,
I tried the partitioning scenario but I've got into
the same problem. The max function is not using the
indexes on the two partitioned tables...
Any other thoughts?
--- Ioana Danes <[EMAIL PROTECTED]> wrote:
> Thanks a lot I will give it a try.
>
> --- Dimi
Thanks a lot I will give it a try.
--- Dimitri Fontaine <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Le mercredi 18 octobre 2006 21:51, Ioana Danes a
> écrit :
> > I am doing a test for a scenario where I have 2
> > schemas one (public) for the operational data and
>
Hi everyone,
I am doing a test for a scenario where I have 2
schemas one (public) for the operational data and
another one (archive) for old, archived data. So
basically I want to split the data from some huge
tables in two. All data before 2006 in archive and all
data after and including 2006 i
Hi everyone,I posted this question some time ago and I did not get any answer so here I am again. Does anyone now what the problem is with the following select when upgrading to postgresql 8.1.4 the query plan does not use the indexes as in postgresql 8.0.3. Here are the results of my que
Filter: (testid IS NOT NULL) Total runtime: 0.159 ms# select max(TESTID) from TEST where TESTTYPE = 1455; max -- 18527829Time: 1.029 ms Thank you very much, Ioana Danes Chris <[EMAIL PROTECTED]> wrote:You've left out the best details. Post an 'expl
I have a problem with a query that in postgres 7.4 and 8.12 has an acceptable response time but in postgres 8.14 is very slow. This is the table I use: create table TEST ( TESTID INT8 not null, TESTTYPE INT4 null, constraint PK_TESTID primary key (TESTID))
I have a problem with a query that in postgres 7.4 and 8.12 has an acceptable response time but in postgres 8.14 is very slow. This is the table I use:create table TEST ( TESTID INT8 not null, TESTTYPE INT4 null, constraint PK_TESTID primary k
13 matches
Mail list logo