"Paul C." <[EMAIL PROTECTED]> writes:
> Indeed, the cost to look up a single string in the st_fti
> table is way high:
> select * from st_fti where string ~ '^kepler';
> costs 36703.40, AND its doing a Seq Scan on st_fti, even though an index
> exists.
Have you done a VACUUM ANALYZE on st_fti
On Wed, Aug 15, 2001 at 05:11:28PM -0700, Scott Holmes wrote:
> It would seem that my database has unseen garbage in the field being queried.
> On further testing I find that
>
> select *
> from people
> where peopcode LIKE 'AB%AH%'
> order by peopcode;
>
> works, however
>
> select *
> f
oops. Too late to use that option; but thanks!
Andrew Gould
--- Justin Clift <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> These functions were indeed created by PgAdmin. It
> seems to create
> tables, functions, triggers and views (maybe rules
> too, not sure) going
> by the name pgadmin_xxx a
On Tue, Aug 21, 2001 at 10:25:35AM +0200, Tony Grant wrote:
>
> > > For example, say I've got a postgresql database of client information
> > > (names, addresses, etc.), and I want to use this information to generate
> > > envelopes for mailouts. As far as my understanding goes, such
> > > funct
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> I have two related questions about joins.
> One is that if you don't group with parenthesis, what order are they
> done in?
Left to right. A JOIN B JOIN C == (A JOIN B) JOIN C.
> Will the optimizer be able to pick the better order of the two possibl
On Wed, Aug 22, 2001 at 11:54:43AM -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > I have two related questions about joins.
>
> The latter. See
> http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/explicit-joins.html
Thanks, this is what
I think the problem is that the indexes on the words are not usable for
regular expression matching. If the words are folded to lower case
when the index is built, then using an exact match (or even like) should
be much faster.
---(end of broadcast)
Andrew Gould writes:
> Notice: function "pgadmin_get_rows" is not dumped.
> Reason: return type name (oid 87589805) not found.
> Notice: function "pgadmin_get_sequence" is not dumped.
> Reason: return type name (oid 87589772) not found.
>
> Does this simply mean that these functions will not be
>
Meant to send this to the whole list...
I had vaccum'ed it, but not 'vacuum analyze' -ed it. That did the trick.
Cost down to 12.09 from 80628.92.
Thank you!
>From: "Mitch Vincent" <[EMAIL PROTECTED]>
>To: "Paul C." <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
>Subject: Re: [GENERAL] FTI is rea
Hi Andrew,
These functions were indeed created by PgAdmin. It seems to create
tables, functions, triggers and views (maybe rules too, not sure) going
by the name pgadmin_xxx and pga_xxx
I'm pretty sure from looking at PgAdmin 7.1.0 recently it has a menu
option to remove it's tables and other c
No.
- Original Message -
From: "jose" <[EMAIL PROTECTED]>
To: "Postgres" <[EMAIL PROTECTED]>
Sent: Wednesday, August 22, 2001 3:51 AM
Subject: [GENERAL] maximum query length
> Hi all,
>
> I have a problem related with the maximum query length
> ERR: query is too long. Maximum length
Did you vacuum after
populating the tables?
If not you should do it
On Wed, Aug 22, 2001 at 11:08:55AM -0400, Paul C. wrote:
> Greetings,
> I am trying to test out the performance of the contrib/fulltextindex
> package and I am getting horrid performance results.
> The Setup:
> I created a
On Tuesday 21 August 2001 15:16, Carlos Felipe Zirbes wrote:
> You alway seemed to me a very reasonable and smart person, but to suggest
> that just because Fernando Lozano is in Brazil he "may not have even a
> Pentium" is, to say the least, a terrible proof of ignorance and prejudice.
Whoa.
I
Greetings,
I am trying to test out the performance of the contrib/fulltextindex
package and I am getting horrid performance results.
The Setup:
I created a simple table, ST (id SERIAL, body varchar(1024), which is to be
searched. I created the ST_FTI table, trigger and indices as per
instruc
During a pg_dump, I got the following messages:
Notice: function "pgadmin_get_rows" is not dumped.
Reason: return type name (oid 87589805) not found.
Notice: function "pgadmin_get_sequence" is not dumped.
Reason: return type name (oid 87589772) not found.
Does this simply mean that these functio
Miroslav Koncar <[EMAIL PROTECTED]> writes:
> 'sql:2001-08-21db.out:5: ERROR: copy: line 1, Bad abstime external
> representation '\N
> psql:2001-08-21db.out:5: PQendcopy: resetting connection
Given the weird line-wrapping of the message, I'm going to bet that the
problem is that newlines in the
Jeff Davis <[EMAIL PROTECTED]> writes:
> I made some simple functions that create the operators + and - for any
> combination of int4's and bool's.
> My question is two-part:
> 1) Is this a sane approach?
It'd be less work if you made a bool->int conversion function and relied
on the regular in
Hi all,
I'm trying SELECT FOR UPDATE
but I have a problem with locks.
example:
I have two users accessing to the same records, say...
user1:
DELECT * FROM table WHERE field=value FOR UPDATE
---
user2:
DELECT * FROM table W
Hello,
I'm a newbie in the postgreSQL world, so if I'm asking what's rather
straightforward, I appologize.
This is what I'm trying to do: my collegue and I have set up three
postgreSQL databases; he has set it up on Linux RedHat 6.2, and I've
been working on RedHat 6.2 as well on Solaris 7. We a
> Hi all,
>
> I have a problem related with the maximum query length
> ERR: query is too long. Maximum length is 16382
> I'm using PostgreSQL 6.5.3 and python
> Is this limit in the newer releases of PostgreSQL too?
> Thanks for any help
All those limits are gone. Upgrade to 7.1.3.
--
Bruc
FYI -- JDBC questions should go to the pgsql-jdbc mail list.
As for your problem, I think probably the easiest workaround is to
explicitly cast your constants. Assuming you are using
PreparedStatements, a statement of the following form should work:
select * from foo
where bar = ?::numeric
W
Hi!
I have to migrate application from Delphi/MSSQL to Kylix/.
One of things used in this app is INSERTED/DELETED tables in triggers.
It's something like NEW and OLD records, but may contain multiple rows.
My questions are:
How difficult would it be to implement such a feature in PostgreSQL?
Wha
Hi all,
I have a problem related with the maximum query length
ERR: query is too long. Maximum length is 16382
I'm using PostgreSQL 6.5.3 and python
Is this limit in the newer releases of PostgreSQL too?
Thanks for any help
Jose Soares
---(end of broadcast)--
23 matches
Mail list logo
