Hi,
I'm thinking about, what might be faster on SELECTs: a column with index
which is NOT NULL and takes the value of 0 or a column which can take
the NULL value instead of 0, also with index.
My feeling sais, that 0 and NOT NULL should be a lot more faster, but
perhaps it's not true?
bye
Al
"Brett W. McCoy" <[EMAIL PROTECTED]> writes:
> On Sun, 10 Dec 2000, Matthew wrote:
>> [Matthew] Would it make sense for postgre to have a mysql
>> compatibility module? An add on package (perhaps in contrib) that
>> would add many of the functions that mysql has that postgre does not.
> I think
> On Sun, Dec 10, 2000 at 12:37:52AM +0900, Tatsuo Ishii wrote:
> > I found a silly bug with src/backend/utils/adt/like.c. Can you try out
> > attached pacthes?
> It looks good. pgsql doesn't crash now. thank you.
Ok, I will commit the pacthes.
--
Tatsuo Ishii
On Sun, 10 Dec 2000, Matthew wrote:
> > I think MySQL got a big start by migrating mSQL users years ago and
> > having a compatibility module for mSQL.
> >
> [Matthew] Would it make sense for postgre to have a mysql
> compatibility module? An add on package (perhaps in contrib) that would
> > The bottom line is that the marketing of PostgreSQL is not even close to
> > that of MySQL. Thank god the code, community and support doesn't follow
> > suit!
>
> I think MySQL got a big start by migrating mSQL users years ago and
> having a compatibility module for mSQL.
>
[Matthew
Uro¹ Gruber <[EMAIL PROTECTED]> writes:
> I started postgres with -i switch, but when i kill the proces i can't
> start it anymore on the same port. I tried this five times and i can
> start it now on 5 ports because i have to use everytime a new port.
> FATAL: StreamServerPort: bind() failed: Ad
> Yes, this would be normal. Due to the fork nature of the backend, you
> will see with ps, depending upon traffic, the actual postmaster fork
> before the backend (postgres) is exec'd. I don't see that here due to my
> use of a pooling webserver, but non-pooled situations will have backends
We
On Sun, 10 Dec 2000, Uro¹ Gruber wrote:
> I started postgres with -i switch, but when i kill the proces i can't
> start it anymore on the same port. I tried this five times and i can
> start it now on 5 ports because i have to use everytime a new port.
>
> I look in my /tmp and try to delete pos
[ Charset ISO-8859-1 unsupported, converting... ]
> The article also mentions enhancements for 7.0 and things coming in the next
> major release (write-ahead or redo logging, outer joins, the removal of row
> size).
>
> They also say it has a well organized development team. ;)
[ Blush ]
--
Hi!
I started postgres with -i switch, but when i kill the proces i can't
start it anymore on the same port. I tried this five times and i can
start it now on 5 ports because i have to use everytime a new port.
I look in my /tmp and try to delete postgres files, but still don't
works. There is n
> On Mon, 4 Dec 2000, Nancy Ellman wrote:
>
> > However, while I have been able to see the results of the first
> > example with
> >
> > \dd mytable
>
> Try \d+ mytable
I have added a mention of \d+ to the comment manual page. I realize \dd
and \d+ are kind of confusing bcause one sh
> The bottom line is that the marketing of PostgreSQL is not even close to
> that of MySQL. Thank god the code, community and support doesn't follow
> suit!
I think MySQL got a big start by migrating mSQL users years ago and
having a compatibility module for mSQL.
--
Bruce Momjian
Philip Crotwell <[EMAIL PROTECTED]> writes:
> Is there significant overhead involoved in using large objects that aren't
> very large?
Yes, since each large object is a separate table in 7.0.* and before.
The allocation unit for table space is 8K, so your 10K objects chew up
16K of table space.
Hi
I'm putting lots of small (~10Kb) chunks of binary seismic data into large
objects in postgres 7.0.2. Basically just arrays of 2500 or so ints that
represent about a minutes worth of data. I put in the data at the rate of
about 1.5Mb per hour, but the disk usage of the database is growing at
On Sun, Dec 10, 2000 at 12:37:52AM +0900, Tatsuo Ishii wrote:
> I found a silly bug with src/backend/utils/adt/like.c. Can you try out
> attached pacthes?
It looks good. pgsql doesn't crash now. thank you.
--
Bye
Juriy Goloveshkin
On Sunday 10 December 2000 07:23, Abe wrote:
> This is probably an easy question for most but here goes:
>
> I am using PHP3 and postgres 6.5
>
> I am trying to do a search on a peoples database and it works fine except
> for the fact that I want to make it case insensitive as some in the
> databa
Abe: It's an SQL thing or a scripting thing. It's probably easiest and
safest in the SQL:
select firstname, surname from employees
where upper(firstname) like upper('%$criteria%') or
upper(surname) like upper('%$criteria%')
That is, force the column and the search string to upper
Thanks David,
works a treat!
Abe
- Original Message -
From: "Hancock, David (DHANCOCK)" <[EMAIL PROTECTED]>
To: "'Abe '" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, December 10, 2000 12:48 PM
Subject: RE: [GENERAL] Simple Question: Case sensitivity
> Abe: It's an SQL thing
This is probably an easy question for most but here goes:
I am using PHP3 and postgres 6.5
I am trying to do a search on a peoples database and it works fine except
for the fact that I want to make it case insensitive as some in the database
are Smith and some are jones. Is this a scripting thi
19 matches
Mail list logo
