I've seen this a few times. It usually results from an unescaped
embedded apostrophe, e.g.,
INSERT INTO ybsc_note (rem) VALUES ('This don't work 'cuz there ain't no
escapes or backslashes around my single quotes.');
Cheers,
Ed Loehr
pawel wrote:
> Hi,
> I have a problem with populating the f
Excellent point, your last comment gives me a tangible incentive for using
hash instead of btree. Since I don't need to use other operators than '=',
there is really no need to spend extra time creating a btree while all I
need is a hash table. In the end, both are as fast for searching, but I
gai
> Excellent point, your last comment gives me a tangible incentive for using
> hash instead of btree. Since I don't need to use other operators than '=',
> there is really no need to spend extra time creating a btree while all I
> need is a hash table. In the end, both are as fast for searching, b
> My results were exactly the same for btree and hash, even when vacumming
> between each index creation. Here's my query:
> SELECT * FROM prod_base WHERE mid='2';
>
> Here's my result:
> Index Scan using prod_mid_idx on prod_base (cost=2.05 rows=2 width=120)
>
> My database is perhaps not big e
My results were exactly the same for btree and hash, even when vacumming
between each index creation. Here's my query:
SELECT * FROM prod_base WHERE mid='2';
Here's my result:
Index Scan using prod_mid_idx on prod_base (cost=2.05 rows=2 width=120)
My database is perhaps not big enough to run som
Run some performace tests and let us know.
> I've been reading the postgresql manual and I find there is very little
> discussion about hash compared to btree. Most of the focus seems to be on
> using btree indices even that the default for 'create index' is btree
> also. From the documentation,
Hi,
I have a problem with populating the following table
CREATE TABLE ybsc_note-- The Bright Star Catalogue Notes
( nid int NOT NULL, -- local id
ybscid int NOT NULL, -- YBSC id number
cat char(4),-- Category
rem char(120), -- Remark
primary key(nid)
);
I've been reading the postgresql manual and I find there is very little
discussion about hash compared to btree. Most of the focus seems to be on
using btree indices even that the default for 'create index' is btree
also. From the documentation, it seems the only difference between either
searchin
Hi, Postgres guru,
I am new to Postgres and just downloaded the source to compile on my
Caldera 2.2.5. I got a trouble and here is what i did (follwoing the
INTALL file):
Hardware : Pentium 200 with 32M ram, 2.1G HD(Linux partition)
1)Add a new account postgres
2)make dir /usr/scr/pgsql
When I couldn't even get my own newly added printfs to show up, that was the
tipoff. Redhat 6.1 installs postmaster in /bin. I didn't know it, and have
been building/installing elsewhere. /bin, of course, is first in my PATH,
before *my* pgsql install bin. Ouch. Timestamping is now working.
Is there a way to make queries using the 'like' operator quicker, more
specifically for queries that look like:
select name from table where name like '%abc%';
Thanks,
Marc
Ed,
Configure will used cached values if config.cache is available so you may
consider first doing a "make distclean", which is the mother of all
cleanouts. Then do the ./configure, 'make', and 'make install'.
I have not yet configure SYSLOG for use, so I redirect all output from the
postmaster
Thanks, Phil. Still, the good mojo escapes me. Time to cut my losses.
I commented USE_SYSLOG back out, then twiddled elog.h, twiddled config.h after
./configure (configure builds a new config.h), tried a few variation on
pg_options, all while bringing down postmaster, running 'make clean', 'mak
Oh, one more thing. I've always made the edit BEFORE running ./configure.
Phil Culberson
-Original Message-
From: Culberson, Philip
Sent: Friday, December 17, 1999 11:42 AM
To: 'Ed Loehr'; [EMAIL PROTECTED]
Subject: RE: [GENERAL] How to get timestamped pgsql logging?
Ed,
My own note
Ed,
My own notes on how to get timestamped error logs refer to the file
"...src/include/utils/elog.h". There is a commented out "#define
ELOG_TIMESTAMPS" line in that header as well. Since version 6.4, I have
always uncommented THAT line and I get timestamps in my error logs... can't
tell you wh
Hi,
On Mon, 13 Dec 1999 10:36:02 -, "Mark Alliban" <[EMAIL PROTECTED]> wrote:
> I have just installed PostgreSQL on SCO OpenServer 5.05 but I am having =
> problems creating a database. My pg_hba.conf file reads:
>
> localall trust
> host
hi all!
i have 2 boxes in my local net:
192.168.1.1 - linux 2.2.12/postgres 6.5.3
192.168.1.2 - windows 98+postgres_odbc+MS Access 97
i want use my postgres database in 3 ways:
- via psql,
- with libpq,CGI,HTTP -> MS Explorer on my Win boxe
- with ODBC on MS Access
the problem is that my linux
> Hello all
>
> On another mailing list unassociated with postgres, someone posted a message
> indicating that in version 7.x, the 8k limit for tuple size was going to be
> eliminated. Can any of the developers confirm this?
>
> Thank you for your time.
Man, we can't keep any secrets. :-)
Unt
Mark,
I think your best bet for a solution to the index problem would be
posting a question to the sql mailing list , because I don't have a
solution to that .
1) The current postgresql source tree (Version 6.5.3) doesn't recognize
support for shared libraries under
SCO Openserver 5.0.5 .
On Fri, 17 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:
> Hi,
>
> I'm vacuming a table containing 300,000 rows with a single index.
> Currently it is taking 1.5 hours to complete. It was faster earlier.
> I have dropped and recreated and reloaded this table. THis does not seem to
Hi,
I'm vacuming a table containing 300,000 rows with a single index.
Currently it is taking 1.5 hours to complete. It was faster earlier.
I have dropped and recreated and reloaded this table. THis does not seem to
help.
Further... vacuum returns several messages like crashed... unused...
mo
Wim Ceulemans <[EMAIL PROTECTED]> writes:
| rpm -q lib gpp reports:
| libgpp-991012-3
|
| And of course I had installed gpp and libgpp. I tried removing and
| re-installing them but this doesn't help.
Okay, maybe some other parts are still to be installed; e.g., you'll
need egcs, of c
Mark Alliban wrote:
>
> Hi,
> Thanks for the suggestion! I've been trying to get it to work for ages and
> using the -h option was the workaround I was looking for.
>
> However I still have a small problem, in that when I do "CREATE UNIQUE INDEX
> AcT_AcNo ON AccountTable (AccountNo);" where Ac
Hi,
Thanks for the suggestion! I've been trying to get it to work for ages and
using the -h option was the workaround I was looking for.
However I still have a small problem, in that when I do "CREATE UNIQUE INDEX
AcT_AcNo ON AccountTable (AccountNo);" where AccountNo is NUMERIC or DECIMAL
I get
Hello All,
Is it possible to change the behavior of operator "=" for text? I
wolud like to redefine this operator in order to it compare strings
without checking of letter case.
I tried the following:
create function TextEqual(text, text)
returns bool
as '
begin
if texteq(upper($1), up
Sorry Peter, I don't say you any thing, I'm using psql on win95.
1. I see psql for Linux requires \N only for data fields with null
values other fields (char,int,etc)
doesn't need \N. Why ?
2. psql for M$Windows95 has a different behavior. For example I can't
insert date fields even using \N
26 matches
Mail list logo
