mitch <[EMAIL PROTECTED]> writes:
> Is there a size limit on indexable varying character fields?
1/3rd page, about 2700 bytes, if you're using btree index.
Presently, TOAST does not help any :-(
regards, tom lane
Hi all:
Is there a way to pass a tablename as a parameter to a SP?
I'll try to explain myself. I want to create a SP that can, for
instance, do a delete from .. so that any particular application all
it has to do is call the SP sending the table to be deleted.
Right now I have:
Hello everyone, I just joined the list. Adam Lang convinced me when he got
some answers for me from your list and sent it to the PHP PG list.
Thanks for all of your input. Let me change my question somewhat to clear up
my concern. How much of a write performance hit will I take if I create
Is there a size limit on indexable varying character fields?
I need a semi-large varchar field (say 2048 characters) but really need
the speed of an index in searching, I'm left wondering at what point
indexing varchar fields becomes useless (if it ever does)..
Thanks!
-Mitch
"Adam Lang" <[EMAIL PROTECTED]> forwards:
>> In Postgres I am forced to create three indicies: one including all
>> three columns, one for col2 and col3, and one for just col3.
Depending on what his queries actually are, perhaps it's sufficient
to create one index on (col3,col2,col1), rather than
Oh, I just made sure that I started a new transaction :)
I actually prefer that timestamps are handled that way... once I realized
*why* I had triggered INSERTs that were stamped 45 minutes earlier than I
thought they should have been.
Greg
> Yes, and that's a feature :)
>
> If you want a wall
Yes, and that's a feature :)
If you want a wall clock time, use timenow()
-alex
On Thu, 8 Feb 2001, Gregory Wood wrote:
> > columns with default timestamp('now') see to be
> > defaulting to the time I started posgresql!
>
> I noticed that timestamps (in my case CURRENT_TIMESTAMP) are taken fr
Title: RE: [GENERAL] Fw: [PHP] Fooling the query optimizer
Running this query:
"SELECT * WHERE col3 = x"
with a btree index on (col1, col2, col3) cannot be performed in an efficient manner, in any database, because you have specified the column order to be col1, col2, col3. If somebody cl
What does:
EXPLAIN
SELECT
tblSIDEDrugLink.DrugID,
tblSIDEDrugLink.MedCondID,
tblMedCond.PatientName AS MedCondPatientName,
tblMedCond.ProfessionalName AS MedCondProfessionalName,
tblSIDEDrugLink.Frequency,
tblSIDEDrugLink.SeverityLevel
FROM
Stephan,
Here is what EXPLAIN shows:
NOTICE: QUERY PLAN:
Sort (cost=0.02..0.02 rows=1 width=64)
-> Nested Loop (cost=0.00..0.01 rows=1 width=64)
-> Seq Scan on tblmedcond (cost=0.00..0.00 rows=1 width=36)
-> Seq Scan on tblsidedruglink (cost=0.00..0.00 rows=1 width=28)
All right ... after reading up on the documentation for vacuum, I
understand why that's necessary. I've run vacuum analyze on all the
tables, now. Here are the more realistic results from explain:
NOTICE: QUERY PLAN:
Sort (cost=62.46..62.46 rows=14 width=64)
-> Nested Loop (cost=0.00..62
Hi,
I am running PGSql 7.0.3 over Linux 2/ELF with a ReiserFS
filesystem,
Bi-P3 800 and 2Gb of RAM.
My database jump from 8 in load to 32 without any real reason
nor too
much requests.
I already do vacuum even on the fly ifever that can decrease
load, but
nothing...
Culley Harrelson <[EMAIL PROTECTED]> writes:
> columns with default timestamp('now') see to be
> defaulting to the time I started posgresql!
try using: default 'now' instead of: default timestamp('now') in your
table definitions. The latter is evaluated by postgres just once, when
the table is i
Greetings All,
I've seem some references to TOAST in 7.1. Can anyone tell me what it is
and/or where I can read all about it and how it will solve all my problems
using BLOBs with PostgreSQL?
Thanks!
David
FYI - I let the query run for 11.5 minutes before killing it off. It
had consumed 11 minutes, 18 seconds of CPU time (reported by ps). The
following messages are from the server log, I'm pasting in all messages
directly following the query:
010208.10:04:29.473 [24041] ProcessQuery
010208.10:15:
On another list, someone posted this question. Are they correct, old
problem, etc.? I'll pass whatever info there is back to the originating
list.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
- Original Message -
From: "Brent R.Matzelle"
Followup:
This query, run against the same dataset in a MS Access 2000 database,
returns immediately with the resultset. (I truly mean immediately) The
computer running the Access db is a laptop, PII 266 w/ 128MB RAM (an old
Dell Latitude). The server running PostgreSQL is a dual PIII 450 w/
2
> columns with default timestamp('now') see to be
> defaulting to the time I started posgresql!
I noticed that timestamps (in my case CURRENT_TIMESTAMP) are taken from the
beginning of a transaction. You didn't mention how you were accessing the
database, but if you were updating everything insid
columns with default timestamp('now') see to be
defaulting to the time I started posgresql!
What am I doing wrong here? Is it an os problem?
Need these columns to capture the current date and
time.
Culley
__
Do You Yahoo!?
Get personalized email
Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> Sometimes I want it literal too. e.g. I'm searching for car I want car and
> nothing else.
Of course, you want this as well.
> In the end it seems too complex. I'm starting to think it may be better to
> keep things literal but fast, and do the smart
The following query:
SELECT
tblSIDEDrugLink.DrugID,
tblSIDEDrugLink.MedCondID,
tblMedCond.PatientName AS MedCondPatientName,
tblMedCond.ProfessionalName AS MedCondProfessionalName,
tblSIDEDrugLink.Frequency,
tblSIDEDrugLink.SeverityLevel
FROM
> I've got a problem - I need a little help. I'm using 6.5.3 from Debian
> stable.
> I've got a database, which has some fields in one table that need to hold a
> fair bit of text (say, 8000-10,000+ characters). Right now, I've got those
> fields as simple text.
[ Martin suggests breaking up the
Emmanuel Charpentier writes:
> Hence a question : shouldn't the system (pg_* and pga_*) tables be somewhat
> documented at least in the reference manual (and maybe cross-referenced in the
> programmer's manual) ? They seem not to be at the time ...
http://www.postgresql.org/devel-corner/docs/pos
[EMAIL PROTECTED] wrote:
> This works well for things like notes and memo's but probably not so good
> for
> huge amounts of data. Its flexible and there's no hardcoded limit to the
> length of data.
Sounds something like TOAST, part of PostgreSQL 7.1, to be released
soon. TOAST, however, is in
Cool, that worked. Thank you.
-Brice
"Brett W. McCoy" wrote:
>
> On Thu, 8 Feb 2001, Brice Ruth wrote:
>
> > Its not working ... I looked at the admin docs and edited the pg_options
> > file appropriately ... the following is what appears in /var/log/messages:
> >
> > postgres[23686]: read_pg
"[EMAIL PROTECTED]" wrote:
> Where can I find postgresql-7.0.x.mips.rpm for my Qube 2??
> I try to find them on the FTPs but I have seen anything
We have no MIPS RPM's available on our FTP site. More specific
information on OS, libc version, kernel, etc would be required anyway.
This is becau
Believe it or not we have the same problem with DB2 on AS/400
In PG you can create large objects which is the proper answer but
there is another way...
A memo table.
This just contains a key to link up to the master record and a sequence
and a long text field, e.g. 6K.
Then write a function tha
On Thu, 8 Feb 2001, Brice Ruth wrote:
> Its not working ... I looked at the admin docs and edited the pg_options
> file appropriately ... the following is what appears in /var/log/messages:
>
> postgres[23686]: read_pg_options: verbose=2,query=4,syslog=2
>
> But no queries ... I sent SIG_HUP to p
Hello,
Where can I find postgresql-7.0.x.mips.rpm for my Qube 2??
I try to find them on the FTPs but I have seen anything
please message me
thanks
__
Voila vous propose une boite aux lettres gratuite sur Voila Mail:
http://mail.voila.fr
Its not working ... I looked at the admin docs and edited the pg_options
file appropriately ... the following is what appears in /var/log/messages:
postgres[23686]: read_pg_options: verbose=2,query=4,syslog=2
But no queries ... I sent SIG_HUP to postmaster, even restarted
postmaster. The file /
Hi folks,
I've got a problem - I need a little help. I'm using 6.5.3 from Debian stable.
I've got a database, which has some fields in one table that need to hold a
fair bit of text (say, 8000-10,000+ characters). Right now, I've got those
fields as simple text.
When I try to enter data into
Quoting Einar Karttunen <[EMAIL PROTECTED]>:
> I think that modules like this could be included in the distribution or
> archieved at the ftp. They'd make it easier for people new to sql to
> start using postgresql. Also there would be no performance loss in
> the backend code, as these "modules"
At 15:47 07.02.2001 +, Richard Huxton wrote:
>[...] It is treating "100.200" as float and can't find an '=' operator that
>matches numeric with float. You can handle it with
>
>where col3=100.200::numeric
Yes, we can, but Access cannot, I have not found out how Delphi can, either.
If You Quot
33 matches
Mail list logo
