Обсуждение: Postgresql and uPortal

Greetings,

We are beginning to implement uPortal on  Postgresql 7.4.8 on a z/Linux server. We are interested in obtaining information pertaining to any modification of the configuration parameters as distributed with the DBMS. Can anyone provide details on changes made such as:

- adjustments in physical space allocation
- adjustments in virtual space allocation - shared buffers, cache sizes etc.
- changes in database management parms
- changes in other system parms
- any modification to any of the tables such as adding indexes
- use connection pooling or not
- logging or not
- performance and tuning tips
- how frequently do you vacuum the database or do you use the auto feature
- are there any locking issues and what are your settings.

Any information would be greatly appreciated. Any insights into your best practices would also be appreciated.

Thanks, Bob Given

Boston University
bgiven@bu.edu

Given, Robert A wrote:
>
> Greetings,
>
> We are beginning to implement uPortal on  Postgresql 7.4.8 on a z/Linux
> server. We are interested in obtaining information pertaining to any
> modification of the configuration parameters as distributed with the
> DBMS......

Start by taking a gander at:
http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
and
http://www.powerpostgresql.com/Downloads/annotated_conf_80.html

Why are you using 7.4.8 instead of the current version of PostgreSQL?

Cheers,
Steve

>
> Start by taking a gander at:
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
> and
> http://www.powerpostgresql.com/Downloads/annotated_conf_80.html
>
> Why are you using 7.4.8 instead of the current version of PostgreSQL?
Probably because it is what shipping which his copy of Linux :)

Joshua D. Drake

>
> Cheers,
> Steve
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Given, Robert A wrote:
| We are beginning to implement uPortal on  Postgresql 7.4.8 on a
| z/Linux server. We are interested in obtaining information pertaining
| to any modification of the configuration parameters as distributed
| with the DBMS.
|
| Can anyone provide details on changes made such as:
|
| - adjustments in physical space allocation

What kind of storage are you using? Dedicated DASD or MDISKs, or perhaps
even SCSI? You may be able to achieve results ranging wildly on either
side of the scale, depending on your workload and storage scheme
deployed. Also, what kind of platform? LPAR or z/VM?

| - adjustments in virtual space allocation
| - shared buffers, cache sizes etc.
| - changes in database management parms

You will need to get a very good idea of what your average (database)
working set size is, because you're dealing with several layers of
indirection (IOCP cache, z/VM cache /if any/, z/Linux operating system
cache, page access frequencies) and it is extremely difficult to shoot
wild ducks and actually hit any in such an environment.

In general though, if you have a lot of guests on your machine, the rule
of thumb is, keep storage low, just a tiiiny bit higher than needed to
have the guest machine start paging, or even allow some (smaller) system
areas to be paged out, if it turns out they are seldomly used.

As for z/Linux parameters, PostgreSQL will ideally need page cache the
size of your working set.

| - changes in other system parms

Please specify more specific details on your current system environment.
You have not really given enough information to give any directly
related hints.

Regards,
- --
~    Grega Bremec
~    gregab at p0f dot net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFECEU0fu4IwuB3+XoRAziMAJ48Q2IAg/gsPUBFrvrg960//q8SqgCfdtc3
CAtgJfPZQe5ICR7/6qHL8jY=
=I3Kd
-----END PGP SIGNATURE-----