Recently I read that one of the distinctions between a standard database
and
a columnar one, which led to an increase in its efficiency, was and I
quote:
Only relevant columns are retrieved (A row-wise database would pull
all columns and typically discard 80-95% of them)
Is this true of
I noticed this immediately when using the PostgreSQL tool for examples of
dumps for creating export of database/table structure/data for the
MyJSQLView
application. I considered implementing a similar copy dump, but seems it
would
not be handled properly with SQL statements.
danap.
This is
Array appends are usually a performance hit, as you said. I'm not sure
though with
PostgreSQL. Why not try it with two arrays and see what happens. At
least you would
reducing the single array and the eliminating the append.
danap.
I got the aggregate function for weighted average done. I
of other
languages and if you are looking for a higher performance, that is the
way I would said its going to come about perhaps.
danap.
DMP you did give me an idea on changing how to call the append array
sfunc looks like this
create or replace function wcost_average_sf (numeric[], numeric
Hello Tony,
Perhaps this will help maybe not. Since the original data import
used quotes for the fields then any case was maintained in the
creation of the new table(s) fields(s). Just take your original
import file and remove all the quotes, ,. Re-import and and
PostgreSQL will use all
Hello,
The project MyJSQLView will provided basic support
for array types in PostgreSQL at the next release.
Information is desired from anyone that uses arrays
in PostgreSQL to effect this support. Just a couple
of questions.
1. What Size, 10 or 100's, 1000's of elements?
2. Single or
I was slightly confused. I'm really trying to identify what type
of support the project should provide to array types. Just from
the input so far, it looks like more needs to be done. If 100's to
1000's of elements are in an array type, the application is going
to have some problems. Presently it
