Robert Treat wrote:
Yes. I think the gist of your post was "out of the box postgresql
performed like garbage compared to mysql, but then i spent some time
tweaking and tuning, taking advantage of indexes, and now it performs so
quickly that i am unable to make any changes within mysql to match
post
Jan Wieck <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Fields earlier in the table definition (further to the left) are
>> marginally faster to access than ones further to the right. I doubt it
>> would be real noticeable unless you had hundreds of fields altogether.
> Do we still "cache" fie
On Tuesday 25 November 2003 07:22 pm, Gaetano Mendola wrote:
> Sander Steffann wrote:
> > Sorry for the inconvenience I caused by disabling the debuginfo package!
> > Sander.
> Is this also related to the fact that gdb on libraries of RH9.0 don't
> complain about the debugging info ?
I would thin
On Tuesday 25 November 2003 07:56 pm, Sander Steffann wrote:
> It turns out that preventing RH9 from building the debuginfo package also
> prevented it from stripping the binaries.
Ah, ok.
> This was what caused the big
> difference in filesize. I have rebuilt the RPMs for RH9 and put them on
> h
Tom Lane wrote:
"D. Stimits" <[EMAIL PROTECTED]> writes:
I'm not looking for an exact answer here, but instead something more
"rule of thumb". If I have a table with many fields, and I retrieving
small groups of fields during a SELECT, whereby the groups of fields are
indexed and/or clustere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually in this case you don't have a hole.
Yes you created the next policy (in this case, may be any similar situation).
But the customer already signed the contract. This means even if he opts out
of it, a record has to be kept. In some areas this
It seems to me there is a confusion about identifiers. There is the primary
key of the table which should be a sequence and may have holes. Seperate
from that is the CustomerFriendlyID which is an ID you can assign and
reassign at your leasure. For a bank, the statement numbers all start from one
f
How can you avoid holes?
Unless you void policies that people cancel halfway through the process
? How is that different than rollback?
Lets say that the customer goes through the motions and after signing
the papers, and then during the cooling off period (mandatory in Canada)
decides he really
Sander Steffann wrote:
Hi,
It turns out that preventing RH9 from building the debuginfo package also
prevented it from stripping the binaries. This was what caused the big
difference in filesize. I have rebuilt the RPMs for RH9 and put them on
http://opensource.nederland.net/.
I had to make a sma
Hi,
It turns out that preventing RH9 from building the debuginfo package also
prevented it from stripping the binaries. This was what caused the big
difference in filesize. I have rebuilt the RPMs for RH9 and put them on
http://opensource.nederland.net/.
I had to make a small modification to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Obviously depends on the carrier. Lloyds for example doesn't allow numbering
gaps. But as said: doing it in a fully isolated stored proc usually works.
The stp I use also assembles the alpha part, so I end up with something like
AA-0001234 in a fixe
Baldur Norddahl <[EMAIL PROTECTED]> writes:
> Apparently there are two rows with identical primary keys which should not be
> possible. Is this a know problem?
Nope. If you try to REINDEX the primary key index, does it spit up a
duplicate-key failure?
regards, tom lane
-
Hi,
> Something is certainly unusual here. Sander, can you rebuild the RH9 set
and
> see why it is so large? For some reason, I missed how many places were in
> there, and missed the fact that there were multiple megabytes difference.
> Debugging symbols or no, this is big.
The difference in si
DECLARE
RowsAffected INTEGER;
BEGIN
-- DO your statement
GET DIAGNOSTICS RowsAffected = ROW_COUNT;
END
On Tuesday 25 November 2003 02:56 pm, Brian Hirt wrote:
> I'm looking to find out how many rows were effected during an update in
> a trigger. I ran across this message by jan talking abou
"D. Stimits" <[EMAIL PROTECTED]> writes:
> I'm not looking for an exact answer here, but instead something more
> "rule of thumb". If I have a table with many fields, and I retrieving
> small groups of fields during a SELECT, whereby the groups of fields are
> indexed and/or clustered, will I ge
I'm looking to find out how many rows were effected during an update in
a trigger. I ran across this message by jan talking about this feature
possibly being added to postgresql 6.5, but I can't find any reference
to such a feature in the current documentation. Did this ever make it
into pos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
AFAIK no. Vacuum runs in a transaction, so you will only see the effects if it
completed. I think you should run vacuum more often.
It also should work to run vacuum "in operation". i.e. I run vacuum about 4
times a day in an active database. Vacuum
On Tue, Nov 25, 2003 at 12:22:29PM +0100, Baldur Norddahl wrote:
> Hi,
>
> I just noticed something bad in our database:
>
> webshop=# select oid,* from content_loc where id=20488;
>oid | id | locale | name
> -+---++--
> 9781056 | 20488 | any| Ris
And ofcourse, you ran ANALYZE before doing any timings, right?
On Tue, Nov 25, 2003 at 01:08:55PM +0100, Marek Lewczuk wrote:
> Hello,
> I have changed DB from MySQL to PostgreSQL. When I have run my
> application on PostgreSQL it was disaster - it was much slower than
> MySQL...
>
> I have tri
Użytkownik Martijn van Oosterhout napisał:
And ofcourse, you ran ANALYZE before doing any timings, right?
Of course.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Hello,
I have changed DB from MySQL to PostgreSQL. When I have run my
application on PostgreSQL it was disaster - it was much slower than
MySQL...
I have tried to change PG configuration file etc.. no luck. After many
long days of thinking what is wrong I have made several tests with
"EXPLAIN"
Hi,
No, there can be no space after 'any' because the foreign key prevents it (which
you of course could not check since I didn't show the content of the foreign
table).
But anyway, here is the output:
webshop=# select oid,id,'['||locale||']','['||name||']' from content_loc where
id=20488 and lo
Hi,
I just noticed something bad in our database:
webshop=# select oid,* from content_loc where id=20488;
oid | id | locale | name
-+---++--
9781056 | 20488 | any| Rise Part II
9781058 | 20488 | any| Rise Part II
(2 rows)
webshop=# \d content
Socketd wrote:
Hi all
Will autovacuum both VACUUM and ANALYZE all databases, so that I can
delete my script which runs daily: "vacuumdb -a -z"?
Yes it would. One thing it never does is issuing vacuum full.
Shridhar
---(end of broadcast)---
TIP 2:
24 matches
Mail list logo
