JJ> I'm trying to port a database from Oracle to PostgreSQL. I used a perl
script,
JJ> ora2pg to extract the info from Oracle.
JJ> The table data was extracted in alphabetical order. When I attempt to load
it,
JJ> I get referential integrity violations (eg. I attempt to load CUSTOMER, but
JJ
Timothy Smith wrote:
i have the following function in plpgsql giving stynax errors all over
the place.
i have doen createlang on the db, as far as i can see i'm right. is
there anything obviously wrong?
one thing to note is i followed this example
http://www.zigo.dhs.org/postgresql/#insert_or
Salve.
I understand from various web searches and so on that PostgreSQL's MVCC
mechanism makes it very hard to use indices or table metadata to optimise
count(*). Is there a better way to guess the "approximate size" of a table?
I'm trying to write a trigger that fires on insert and performs som
I believe running count(*) means fulltable scan, and there's no way
to do it without it. But what about some "intermediate" table, with
the necessary counts?
That means to create a table with values (counts) you need, and on
every insert/delete/update increment or decrement the appropriate
values.
[EMAIL PROTECTED] writes:
> I believe running count(*) means fulltable scan, and there's no way
> to do it without it. But what about some "intermediate" table, with
> the necessary counts?
There's a fairly complete discussion in the PG list archives of a
reasonably-efficient scheme for maintainin
On Tue, Aug 09, 2005 at 10:49:14PM -0400, Tom Lane wrote:
> Current best practice is to run the explain and parse out the "rows"
> figure using a perl (or axe-of-choice) regexp, though we could be
> persuaded to supply a simpler API if there's enough demand for it.
Somebody else requested a row-co
