I am in process of migrating a database from Pg 7.4.3 to Pg 8.0.3. I
dumped and reloaded the data, and things look good, until I try to
work with it. When I try to make a query to a view based on a large
join (select * from 'view' limit 10), the 7.4.3 query works very
well, and the indexe
I just re-checked, and all the same index definitions are on both
tables.
Cheers,
-albert
On 17.6.2005, at 14:20, Tom Lane wrote:
Albert Vernon Smith <[EMAIL PROTECTED]> writes:
I am in process of migrating a database from Pg 7.4.3 to Pg 8.0.3. I
dumped and reloaded the data, and
I am in process of migrating from Pg 7.4.5 to 8.0.3. I have the same
data loaded in to the two. However, when I do a query on my 8.0.3
installation, I am not getting a very well optimized query. (All the
memory settings are equivalent.)
On 8.0.3, I get the following query plan:
dbsnp_b1
Yes, I did an analyze, and see this behavior.
-albert
On 30.6.2005, at 20:39, Joshua D. Drake wrote:
Albert Vernon Smith wrote:
I am in process of migrating from Pg 7.4.5 to 8.0.3. I have the
same data loaded in to the two. However, when I do a query on my
8.0.3 installation, I am
I have two tables, listed as below. I'm inserting values for "text"
into table "two" (which must already exist as "text" values in table
"one"). When I do that, I'd like to also insert the associated
"one_id" value from table "one" into the field "two.one_id". How is
best to go about tha
xt
= two.mytext);
On 3.1.2006, at 16:07, codeWarrior wrote:
Don't use reserved words for column names.
"Albert Vernon Smith" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
I have two tables, listed as below. I'm inserting values for
"text"
BEFORE INSERT OR UPDATE ON two FOR EACH
ROW EXECUTE PROCEDURE return_one_id()
Voila!
-albert
On 3.1.2006, at 14:36, Albert Vernon Smith wrote:
I have two tables, listed as below. I'm inserting values for
"text" into table "two" (which must already exist as "te
