Well, there's plenty of negatives to not doing it. Like postgresql's
large shared_buffers getting swapped out to make more space for disk
buffers. So, pgsql goes to grab data from shared buffers and has to
wait for the OS to swap them back in.
On Wed, Sep 17, 2008 at 4:28 PM, <[EMAIL PROTECTED]
Is there any negative effects by doing this?
The swappiness is sitting on the default 60 at the moment.
On Wed, 17 Sep 2008 00:46:13 -0600, "Scott Marlowe"
<[EMAIL PROTECTED]> wrote:
> On Tue, Sep 16, 2008 at 11:30 PM, <[EMAIL PROTECTED]> wrote:
>> Hi All
>>
>>
>> I recently made a change to my
Just a thought, but did you compile from the ports? The PostgreSQL
client and server are separate ports on FreeBSD. If I recall correctly,
the updated client typically isn't handled as a dependency when the
server is updated, so you would likely have to handle them separately.
Mel Peterson
R&D Eng
"Guido Barosio" <[EMAIL PROTECTED]> writes:
> Getting to the latest 7.4 server involves the same as going to the
> latest 8.x server, AFAIK, if we take in consideration that 7.4.8
> requires a dump & restore (meaning downtime).
(a) it does *not* require a dump and restore
(b) if you ignore the re
Daniel Christopher <[EMAIL PROTECTED]> writes:
> I compiled from source, and followed the instructions in the
> documentation about upgrading to a new major release (pg_dumpall,
> shutdown, mv old version, install new version, restore)
Well, at that level of detail, it should've worked. So the
> From: dbchristopher <[EMAIL PROTECTED]>
> I upgraded to postgresql 8.3.3 a few weeks ago, and it seems
> that while the
> server was upgraded, but for some reason none of the
> accompanying software
> was (pg_dump, psql, etc)
>
> I get this error when I try to back up the database:
> pg_dump: s
On Wed, Sep 17, 2008 at 2:23 PM, Guido Barosio <[EMAIL PROTECTED]> wrote:
> Where can I buy that t-shirt? :)
>
> Hmm, you are right. My intention was to explain that the case for a
> 7.4.21 (wich AFAIK is the latest one of the 7.4 series) is the same as
> for the v8 series of the server. 7.4.8 seem
Where can I buy that t-shirt? :)
Hmm, you are right. My intention was to explain that the case for a
7.4.21 (wich AFAIK is the latest one of the 7.4 series) is the same as
for the v8 series of the server. 7.4.8 seems to be the latest one
before a dump & restore would be a good idea. That was my po
On Wed, Sep 17, 2008 at 1:43 PM, Guido Barosio <[EMAIL PROTECTED]> wrote:
> Getting to the latest 7.4 server involves the same as going to the
> latest 8.x server, AFAIK, if we take in consideration that 7.4.8
> requires a dump & restore (meaning downtime).
7.4.7 to 7.4.8 does NOT require a comple
On Wed, Sep 17, 2008 at 11:01 AM, M C <[EMAIL PROTECTED]> wrote:
> What are the "maximum" amount of "connections" allowed to "postgres"? and
> what would be a resonable amount of connection/processes to see based on
> user connections?
That really depends on what you're doing with it. If each con
Gee,
Going to Oracle does seem a bit like throwing the baby out with
the bath water. For pretty much any use, we found that Oracle requires
many more hardware and management resources than PostgreSQL needs for
the same performance. Make certain that you load test your Oracle "upgrade"
to ensure th
Getting to the latest 7.4 server involves the same as going to the
latest 8.x server, AFAIK, if we take in consideration that 7.4.8
requires a dump & restore (meaning downtime).
I would rather go after the latest 8.x server
2 cents.
(It seems that Vivek works for Infosys, and that may explain th
What OS are you running on?
How did you perform this upgrade? In a packaged form like rpm? or
did you compile from source?
I am running FreeBSD 6.1
I compiled from source, and followed the instructions in the
documentation about upgrading to a new major release (pg_dumpall,
shutdown,
The maximum number of Postgres connections you can have may be
controlled by adjusting the max_connections PG parameter based on your
anticipated connections needs and requirements.
Make sure that your Kernel's related parameters are also configured
properly to accommodate your max_connection
On Wed, Sep 17, 2008 at 12:31 PM, Kenneth Marshall <[EMAIL PROTECTED]> wrote:
> Gee,
>
> Going to Oracle does seem a bit like throwing the baby out with
> the bath water.
Especially considering the performance increase from pgsql 7.4 to 8.3
is humongous. I'd say most operations are 2 to 4 times a
What are the "maximum" amount of "connections" allowed to "postgres"? and what
would be a resonable amount of connection/processes to see based on user
connections?
--- On Wed, 17/9/08, Jonathan Nalley <[EMAIL PROTECTED]> wrote:
> From: Jonathan Nalley <[EMAIL PROTECTED]>
> Subject: Re: [ADMIN] unable to backup database -- psql not up to date
> To: "dbchristopher" <[EMAIL PROTECTED]>, pgsql-admin@postgresql.org
> Date: Wednesday, 17 September, 2008, 3:23 P
Yes that's true and that's planned. We will migrate to Oracle. But as of now
need some pointers on solving the problem in hand.
Regards,
Vivek
-Original Message-
From: Guido Barosio [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 17, 2008 6:39 PM
To: Vivek_Sharan
Cc: Scott Marlowe
I'm using postgres 7.4.5
Regards,
Vivek
-Original Message-
From: Guido Barosio [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 8:08 PM
To: Vivek_Sharan
Cc: Scott Marlowe; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Heavy postgres process
On Tue, Sep 16, 2008 at 1:41 AM,
On Wed, Sep 17, 2008 at 7:18 AM, Vivek_Sharan <[EMAIL PROTECTED]> wrote:
> Yes that's true and that's planned. We will migrate to Oracle. But as of now
> need some pointers on solving the problem in hand.
Well, updating to the latest 7.4 version would be a very very good
move. There are some ver
On Tue, Sep 16, 2008 at 5:53 PM, dbchristopher <[EMAIL PROTECTED]> wrote:
>
> I upgraded to postgresql 8.3.3 a few weeks ago, and it seems that while the
> server was upgraded, but for some reason none of the accompanying software
> was (pg_dump, psql, etc)
>
> I get this error when I try to back u
I upgraded to postgresql 8.3.3 a few weeks ago, and it seems that while the
server was upgraded, but for some reason none of the accompanying software
was (pg_dump, psql, etc)
I get this error when I try to back up the database:
pg_dump: server version: 8.3.3; pg_dump version: 8.2.6
pg_dump: abor
Well, the answer is shor Vivekt:
Upgrade that postgresql ASAP, it's too way old.
gb.-
On Wed, Sep 17, 2008 at 9:29 AM, Vivek_Sharan <[EMAIL PROTECTED]> wrote:
> I'm using postgres 7.4.5
>
> Regards,
> Vivek
>
>
>
> -Original Message-
> From: Guido Barosio [mailto:[EMAIL PROTECTED]
> Sent
Hi Reddy,
Have you done the entries in pg_hba.conf file and in postgresql.conf file -
listen address. ?
- Vishal
Date: Tue, 16 Sep 2008 00:53:22 -0400From: [EMAIL PROTECTED]: [EMAIL
PROTECTED]: [ADMIN] connecting to serverCC: pgsql-admin@postgresql.org
Hi gb Thanks for your reply, Ya
24 matches
Mail list logo
