On 7/04/2010 12:24 AM, Brian Cox wrote:
On 04/06/2010 01:18 AM, Craig Ringer [cr...@postnewspapers.com.au] wrote:
I'm wondering if the issue is with strace rather than Pg. That is to
say, that strace is trying to print:
Thanks, Craig: I do think that this is a strace issue.
As for what Pg is
On Tue, Apr 6, 2010 at 6:30 PM, Joel Jacobson wrote:
> Actually, swapping the order of the conditions did in fact make some
> difference, strange.
>
> I ran the query a couple of times for each variation to see if the
> difference in speed was just a coincidence or a pattern. Looks like the
> spe
I know this problem crops up all the time and I have read what I could
find, but I'm still not finding an answer to my problem. This is all
postgres 8.3. Yes, I've enabled constraint_exclusion. Yes, there are
indexes on the partitions, not just on the parent.
I've got a table with 1 month partit
*ubomír Varga wrote:
> Hi, stright to my "problem":
Please show the exact problem query and the results of running it
with EXPLAIN ANALYZE, along with the other information suggested
here:
http://wiki.postgresql.org/wiki/SlowQueryQuestions
-Kevin
--
Sent via pgsql-performance mailing list
On Sun, Apr 4, 2010 at 3:17 PM, Lew wrote:
> Christiaan Willemsen wrote:
>>
>> About a year ago we setup a machine with sixteen 15k disk spindles on
>> Solaris using ZFS. Now that Oracle has taken Sun, and is closing up Solaris,
>> we want to move away (we are more familiar with Linux anyway).
>
>
2010/3/31 Ľubomír Varga :
> Hi, stright to my "problem":
> If I try to select constant 1 from table with two rows, it will be something
> like this:
>
> explain
> SELECT * FROM t_route
> WHERE t_route.route_type_fk = (SELECT id FROM t_route_type WHERE type
> = 2)
> limit 4;
>
> "Limi
On Fri, Apr 2, 2010 at 2:19 PM, Joel Jacobson wrote:
> Is this a bug? I'm using version 8.4.1.
It's not really a bug, but it's definitely not a feature either.
> Limit (cost=0.00..43.46 rows=1 width=4) (actual time=1023.213..1023.214
> rows=1 loops=1)
> -> Index Scan using transactions_pke
Greg Smith pisze:
The MegaRAID SAS 84* cards have worked extremely well for me in terms
of performance and features for all the systems I've seen them
installed in. I'd consider it a modest upgrade from that 3ware card,
speed wise.
OK, sounds promising.
The main issue with the MegaRAID ca
On 04/06/2010 01:18 AM, Craig Ringer [cr...@postnewspapers.com.au] wrote:
I'm wondering if the issue is with strace rather than Pg. That is to
say, that strace is trying to print:
Thanks, Craig: I do think that this is a strace issue.
As for what Pg is doing: creat() returns -1 on error and a
I came across a strange problem when writing a plpgsql function.
Why won't the query planner realize it would be a lot faster to use the
"index_transactions_accountid_currency" index instead of using the
"transactions_pkey" index in the queries below?
The LIMIT 1 part of the query slows it down fr
2010/4/1 Bruce Momjian :
> I think one of the problems is that we do the truncate even if the table
> has not be touched by the query, which is poor behavior.
Thank you for the support.
Will be this problem registered?
PS
I see a workaround: switch off "on commit delete rows" on temp tables
and
On Thu, 2010-04-01 at 04:27 +0530, raghavendra t wrote:
> I'm sorry I couldn't come up with more, but what you've
> provided so
> far is roughly equivalent to me telling you that it takes over
> four
> hours to travel to see my Uncle Jim, and then asking you
On Fri, 2010-04-02 at 16:28 -0400, Beaver, John E wrote:
...
> I know that the query used here could have been a COPY statement, which I
> assume would
> be better-behaved, but I'm more concerned about the case in which the query
> is more complex.
COPY can copy out results of a SELECT query a
Christiaan Willemsen wrote:
About a year ago we setup a machine with sixteen 15k disk spindles on
Solaris using ZFS. Now that Oracle has taken Sun, and is closing up
Solaris, we want to move away (we are more familiar with Linux anyway).
What evidence do you have that Oracle is "closing up" So
Hi, stright to my "problem":
explain
SELECT * FROM t_route
WHERE t_route.route_type_fk = 1
limit 4;
"Limit (cost=0.00..0.88 rows=4 width=2640)"
" -> Seq Scan on t_route (cost=0.00..118115.25 rows=538301 width=2640)"
"Filter: (route_type_fk = 1)"
If I try to select c
2010/3/30 Tom Lane :
> I don't recall any operations at transaction start for such tables,
> but there may be some.
>
Both in СommitTransaction(void) and PrepareTransaction(void) we can
see PreCommit_on_commit_actions() call;
Here PreCommit_on_commit_actions()
case ONCOM
Hi Scott,
That sound like a usefull thing to do, but the big advantage of the SAN is that
in case the physical machine goes down, I can quickly startup a virtual machine
using the same database files to act as a fallback. It will have less memory,
and less CPU's but it will do fine for some
17 matches
Mail list logo
