"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> So: show me a use case for this that will still make sense in a
>> mostly-autovacuum world.
> I think you are living in a different world than I am if you think it
> is a mostly-autovacuum world.
Certainly it i
On Nov 30, 2007 4:53 PM, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
> On Nov 30, 2007 5:00 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> > > So: show me a use case for this that will still make sense in a
> > > mostly-autovacuum world.
> >
> > I think you are living in a different world than I a
On Nov 30, 2007 5:23 PM, Chris Browne <[EMAIL PROTECTED]> wrote:
> And why is does it not suffice to do the following?
I'm not saying it doesn't. I'm fine with writing it manually. I'm
talking about making it easy for most users. Remember, we're not
UNIX-only; like it or not, most Windows peopl
[EMAIL PROTECTED] ("Jonah H. Harris") writes:
> On Nov 30, 2007 4:30 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> For what?
>
> Convenience.
>
>> AFAICS we are moving as fast as we can in the direction of auto vacuum
>> and analyze. Adding more frammishes to the manual commands seems like
>> gilding
Hi Jonah,
Many thanks!
>> 2) how would I look at the "open/used" connections?
> select * from pg_stat_activity;
This is a wonderful view! How would I properly terminate
these (of course there are 99 of them!) these query process?
Should I do this from unix or is there any postgres tool I
can u
On Nov 30, 2007 5:00 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> > So: show me a use case for this that will still make sense in a
> > mostly-autovacuum world.
>
> I think you are living in a different world than I am if you think it
> is a mostly-autovacuum world.
Same here.
> Yes autovacuu
Joshua D. Drake escribió:
> Autovacuum is a great utility for many workloads but even with the
> upcoming changes I will continually find myself turning off autovacuum
> for specific relations just so I can turn around and turn on vacuum
> within cron for others.
>
> The multi-worker autovacuum
Am Freitag, 30. November 2007 21.07:40 schrieb Bill Willits:
> We have just upgraded our phppgadmin client from v3.5 to v.4.1.3. Now,
> when we view special characters in phppgadmin they are displayed
> incorrectly. If we update the character field (to a special character), it
> will not store pr
On Fri, 30 Nov 2007 16:48:24 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> > On Nov 30, 2007 4:30 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> >> AFAICS we are moving as fast as we can in the direction of auto
> >> vacuum and analyze. Adding more frammis
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On Nov 30, 2007 4:30 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> AFAICS we are moving as fast as we can in the direction of auto vacuum
>> and analyze. Adding more frammishes to the manual commands seems like
>> gilding the buggy whip.
> Autovacuum w
On Dec 1, 2007 12:46 AM, Campbell, Lance <[EMAIL PROTECTED]> wrote:
> Could you please add to your to do list a schema parameter for vacuum?
>
>
>
> Example:
>
>
>
> VACUUM SCHEMA xyz;
>
>
>
> PostgreSQL would get a list of all of the tables found in the schema. It
> would then loop through vacu
On Nov 30, 2007 4:30 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> For what?
Convenience.
> AFAICS we are moving as fast as we can in the direction of auto vacuum
> and analyze. Adding more frammishes to the manual commands seems like
> gilding the buggy whip.
Autovacuum will never be the be all en
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On Nov 30, 2007 2:46 PM, Campbell, Lance <[EMAIL PROTECTED]> wrote:
>> Could you please add to your to do list a schema parameter for vacuum?
> Schema-based analyze would also be useful.
For what?
AFAICS we are moving as fast as we can in the direc
Many thanks, Usama!
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: Usama Dar [mailto:[EMAIL PROTECTED]
Sent: Fri 11/30/2007 1:24 PM
To: Tena Sakai
Cc: Jonah H. Harris; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection limit exceeded
On Dec 1, 2007 1:34 AM, Tena Sakai <[
Many thanks, Jonah!
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: Jonah H. Harris [mailto:[EMAIL PROTECTED]
Sent: Fri 11/30/2007 1:17 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection limit exceeded
On Nov 30, 2007 3:34 PM, Tena Sakai <[EMAIL PROT
On Dec 1, 2007 1:34 AM, Tena Sakai <[EMAIL PROTECTED]> wrote:
> Hi Jonah,
>
> Many thanks!
>
> >> 2) how would I look at the "open/used" connections?
> > select * from pg_stat_activity;
>
> This is a wonderful view! How would I properly terminate
> these (of course there are 99 of them!) these
Hi,
I also have this issue (I'm using 8.2.4), but whenever this happens
I see only a few (4-6) postgresql processes in the system, and my
connection limit is set to 128. Kinda strange. Next time when I
notice it I will check pg_stat_activity and report back.
On Fri, Nov 30, 2007 at 03:03:31PM -05
Campbell, Lance wrote:
Could you please add to your to do list a schema parameter for vacuum?
Example:
VACUUM SCHEMA xyz;
PostgreSQL would get a list of all of the tables found in the schema.
It would then loop through vacuuming each table in the schema.
I found today that I
On Fri, Nov 30, 2007 at 12:33:41PM -0800, Joshua D. Drake wrote:
> On Fri, 30 Nov 2007 13:46:53 -0600
> "Campbell, Lance" <[EMAIL PROTECTED]> wrote:
>
> > Could you please add to your to do list a schema parameter for vacuum?
> >
> >
> >
> > Example:
> >
> >
> >
> > VACUUM SCHEMA xyz;
> >
On Fri, 30 Nov 2007 13:46:53 -0600
"Campbell, Lance" <[EMAIL PROTECTED]> wrote:
> Could you please add to your to do list a schema parameter for vacuum?
>
>
>
> Example:
>
>
>
> VACUUM SCHEMA xyz;
>
>
+1
Joshua D. Drake
signature.asc
Description: PGP signature
On Nov 30, 2007 2:46 PM, Campbell, Lance <[EMAIL PROTECTED]> wrote:
> Could you please add to your to do list a schema parameter for vacuum?
Schema-based analyze would also be useful.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax
We have just upgraded our phppgadmin client from v3.5 to v.4.1.3. Now, when we
view special characters in phppgadmin they are displayed incorrectly. If we
update the character field (to a special character), it will not store
properly. Our database encoding is SQL_ASCII. The same operations
On Nov 30, 2007 2:55 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
> On my postgres 8.1.1, I get a response
>psql: FATAL: connection limit exceeded for non-superusers
> 1) Is this to do with max_connections setting in the postgres
> configuration file? (my setting is 100 (I think this is t
Hi Everybody,
On my postgres 8.1.1, I get a response
psql: FATAL: connection limit exceeded for non-superusers
A few questions come to mind...
1) Is this to do with max_connections setting in the postgres
configuration file? (my setting is 100 (I think this is the
default).)
2) how wo
Could you please add to your to do list a schema parameter for vacuum?
Example:
VACUUM SCHEMA xyz;
PostgreSQL would get a list of all of the tables found in the schema.
It would then loop through vacuuming each table in the schema.
I found today that I did not have max_fsm_pages set
Hi ALL,
I am trying to restore 2G dump file using pg_restore and it will erros
out with the following message;
pg_restore: [custom archiver] could not uncompress data: too many length
or distance symbol". Has anyone seen this before? I 'd really appreciate
your help.
Thanks,
Dinesh
--
26 matches
Mail list logo
