On Thu, Aug 20, 2015 at 8:19 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
>
> SELECT [...]
> FROM (SELECT reference_id, [...] FROM table_where_referenced_id_is_a_pk
> WHERE reference_id EXISTS/IN/JOIN)
>
> src
> LEFT JOIN type1 USING (reference_id)
> LEFT JOIN type2 USING (refere
Pretty bad subject description... but let me try to explain.
I'm trying to figure out what would be the most efficient way to query data
from multiple tables using a foreign key.
Right now the table design is such that I have multiple tables that share
some common information, and some specific
Greg Smith wrote:
CFQ/Deadline/AS are I/O scheduler choices. What changed completely in
2.6.23 is the kernel process scheduler.
http://people.redhat.com/mingo/cfs-scheduler/sched-design-CFS.txt
gives some info about the new one.
While the switch to CFS has shown great improvements in terms o
Greg Smith wrote:
Note that I've had some issues with the desktop Ubuntu giving slower
results in tests like this than the same kernel release using the
stock kernel parameters. Haven't had a chance yet to see how the
server Ubuntu kernel fits into that or exactly what the desktop one is
do
Luke Lonergan wrote:
pgbench is unrelated to the workload you are concerned with if ETL/ELT
and decision support / data warehousing queries are your target.
Also - placing the xlog on dedicated disks is mostly irrelevant to
data warehouse / decision support work or ELT. If you need to
maxi
I'm trying to run a few basic tests to see what a current machine can
deliver (typical workload ETL like, long running aggregate queries,
medium size db ~100 to 200GB).
I'm currently checking the system (dd, bonnie++) to see if performances
are within the normal range but I'm having trouble
Jared Mauch wrote:
I do large databases in Pg, like 300GB/day of new data.
That's impressive. Would it be possible to have details on your
hardware, schema and configuration and type of usage ?
I'm sure there's something to learn in there for a lot of people (or at
least for me)
Ch
Tom Lane wrote:
This sounds like corrupt data --- specifically, 1664639562 showing
up where a variable-width field's length word ought to be. It
may or may not be relevant that the ASCII equivalent of that bit
pattern is Jb8c ... do you work with data that contains such
substrings?
Not spec
(posting on pgsql-perf as I'm questioning the pertinence of the
settings, might not be the best place for the overall pb: apologies)
Postgresql 8.1.10
Linux Ubuntu: 2.6.17-12-server
4GB RAM, machine is only used for this I do have less than 30 tables, 4
of them having between 10-40 million rows
Hi,
Out of curiosity, can anyone share his tips & tricks to validate a
machine before labelling it as 'ready to use postgres - you probably
won't trash my data today' ?
I'm looking for a way to stress test components especially kernel/disk
to have confidence > 0 that I can use postgres on top
10 matches
Mail list logo
