On Thu, Feb 24, 2005 at 04:20:03PM -0500, Bruce Momjian wrote:
>
> My guess is that you have not ANALYZEd the tables recently and the
> optimizer is making a bad choice.
I think this problem is similar to one a couple of months ago:
http://archives.postgresql.org/pgsql-bugs/2005-01/msg00174.php
On Thu, Mar 03, 2005 at 03:01:10PM +0530, Surabhi Ahuja wrote:
> i have to write a program in C++ using libpq. The program
> establishes a connection with the desired database.
> I have 4 tables in the database. Now i want to get the list of
> attribute names, their data types for each of those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Something very bad has happened to pg_attribute.
Just for a data point, this same problem happened to me on a 8.0
beta database. Actually, only one of 8 databases was affected for that
particular backend, but that one was toast and I had to rebuil
Martijn van Oosterhout writes:
> If someone wants to step up and write the code, well... Bit hard, it
> means that everytime a row is updated the index needs to be updated
> too, gotta get all the corner cases, locking, etc.
Even if someone did step up and write the code, the patch would probably
On Sun, Mar 06, 2005 at 11:54:52PM +0200, Ioannis Theoharis wrote:
> > Visibility information. An index contains references to all rows in all
> > transactions. You need to go back to the table to work out if the row
> > is visible in your transaction.
> >
> > Hope this helpsm
>
> Yes at all.
> Yo
>
> Visibility information. An index contains references to all rows in all
> transactions. You need to go back to the table to work out if the row
> is visible in your transaction.
>
> Hope this helpsm
Yes at all.
You have a lot of work for future postgresql' versions :-))
---
> >
> > As far as i can see, postgresql select a simple "INDEX SCAN using index"
> > on table.
>
> That's because the index does not hold all the information. So INDEX
> ONLY is impossible.
>
Thank you for your quick answer, but there is something a don't
understand:
the index holds all attribu
On Sun, Mar 06, 2005 at 11:39:05PM +0200, Ioannis Theoharis wrote:
> > > As far as i can see, postgresql select a simple "INDEX SCAN using index"
> > > on table.
> >
> > That's because the index does not hold all the information. So INDEX
> > ONLY is impossible.
> >
>
> Thank you for your quick an
On Sun, Mar 06, 2005 at 10:38:22PM +0200, Ioannis Theoharis wrote:
> in case that one has a table R(att0 int4, att1 int4), an index on att1
> and a query selecting only att1 whith a range condition over att1, then
> the optimal access path for a rdbms would be "INDEX ONLY SCAN", which means
> scan
Hi,
in case that one has a table R(att0 int4, att1 int4), an index on att1
and a query selecting only att1 whith a range condition over att1, then
the optimal access path for a rdbms would be "INDEX ONLY SCAN", which means
scan only the index, and not the relation (all the needed information
exi
Ok. Let,s have a some model scenarios . Let it be a web server with some
embedded language like PHP.
1: Multiprocess server (Like Apache 1.x ) : Each process use one persistent
connection. Right ? One proces can serve only one request in present
time. Right ? When request is finished, pro
Title: Message
A
couple of comments:
pgadmin asked you for the postgres database account. NOT for the service
account. The postgres database account is never autogenerated, it is always
entered during the installation (on the initdb page).
To
change a users password in any windows versio
"Sim Zacks" <[EMAIL PROTECTED]> writes:
> I have a view that selects 2 functions, plus other data from a view and 2
> tables.
> A Select * on the join take approximately 1.3 seconds.
> Select function a() from the join takes about 1.3 seconds.
> select function b() from the join takes about 1.3 sec
Hi,
Please use:
convert X: /FS:NTFS
at the command prompt of your Windows XP. (X is the
drive number where you have your Windows system files,
most likely C)
If it asks for force dismount, pick yes.
Reboot the system and allow the System do the
conversion. The conversion is usually done at t
Hi.
I'm looking for a somewhat standardized means of configuring a cluster
of postgres nodes for better performance and availability. I have a SAN
available for data storage.
Can this be done?
Thanks,
Morten
---(end of broadcast)---
TIP 4: Don't
PostGreSQL 8.0Beta1 (yes I know there is a new version, I will upgrade soon)
The 3 Explain Analyze results are at the bottom of the message. I tries
attaching them as text files but it wouldn't take them.
I have a view that selects 2 functions, plus other data from a view and 2
tables.
A Select *
16 matches
Mail list logo
