Can I run something by y'all to see if I'm on the right track, or have fallen
off my rocker?
... Postgresql 7.4 ...
Essentially I want to convert a user to a group. I want this new group to have
the same privileges to the same objects that the original user had. I can then
remove privileges from
I'm using a TiGiJet 2GB Solid State drive. My thought was to place the WAL on
it to speed up writes. I don't know of any tools that exist to determine the
effectiveness of this except for anecdotal analysis (This type of query took 3
minutes yesterday, and 1 minute today) ... Sar gives me machine-w
I need an informed opinion:
The performance boost from clustering is wonderful. But, some tables would have
to clustered several times a day, since there is usually some type of "status"
column that is updated pretty regularly. Clustering is an expensive operation.
If I pulled out that column into
--- "scott.marlowe" <[EMAIL PROTECTED]> wrote:
> On Wed, 5 May 2004, Chris Gamache wrote:
> Have you read:
>
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
>
> yet? It may just be that you don't have enough shared_buffers or whatnot.
Ab
When I run an query (that I have identified as expensive, and non-critical), I
would like to be able to take its priority down a few notches to allow the
standard every-day tasks of the DB to run unhindered. As it stands, postmasters
elbow each other out for processor time, and it seems like one ex
After using Slackware for my production servers for years, I decided to try out
Gentoo. Since it was so easy to download and install, I decided to try to use
the PostgreSQL Ebuild. I just didn't like how and where it installed the
software, so I removed it to go with a src tarball. I'm no Portage
I don't know of any complete list, but I'm sure that there are some clues in
the changelogs.
In the meantime... I'd like to throw in one "gotcha" that set me back some time
when I recently upgraded from 7.2 to 7.4 : You could never use aggregates in
where clauses before. That's what HAVING is fo
rs, functions, and aggregates will operate properly.
CG
--- Harald Fuchs <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> Chris Gamache <[EMAIL PROTECTED]> writes:
>
> > That does make more sense (cents? :) ).
>
> > View and rule still apply,
That does make more sense (cents? :) ).
View and rule still apply, tho. Better performance still?
create temporary table new_money (product text, cents int4);
create view v_new_money as select product, (cents::numeric/100)::numeric(10,2)
as dollars from new_money;
create rule v_new_money_upd a
--- Harald Fuchs <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
>
> > On Fri, Jan 30, 2004 at 10:55:13 -0800,
> > Chris Gamache <[EMAIL PROTECTED]> wrote:
> >> Well, after living
Well, after living with the (depreciated) Money datatype for 5 years, I think
its finally time to say goodbye (and now that we have DROP COLUMN it'll be MUCH
easier transition). What's the preferred monetary datatype? numeric(10,2)?
float4? float8? We're dealing only with US Dollars.
CG
_
I'm having some issues dumping a database from 7.2, reloading it to 7.4.
I'm using the 7.4 pg_dump. The problem I'm having is an issue of internal
object dependancies. For instance I have a_function that uses b_function. The
a_function gets dumped in first, and errors out because b_function hsan't
I have one RAID 1+0 array available. My primary concern is data integrity.
The general instruction is to put pg_xlog on another filesystem, seperated
physically from the database files, for maximum performance. That is what I had
planned on doing. However, it dawned on me that there could be a ser
I'm trying to avoid having to install 7.3, dump 7.2 and reload 7.3, then
install 7.4, dump 7.3 and install to 7.4 ... What's the chances of just using
the 7.4 pg_dumpall on the 7.2 database and having it work 100% ?
Also, I recall that when upgrading from 7.2 to 7.3 there was something that had
t
What's your thought on creating some type of calibration applet that will
divine proper settings for the PostgreSQL performance related variables by
taking into consideration the speed of the machine, amount of RAM, access time
of the filesystem, and the speed of various queries on a standardized (
15 matches
Mail list logo
