On Fri, May 13, 2005 at 10:48:13PM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > We are working on it, and hopefully in 8.1 you will be told where the
> > user/group is referenced if you try to drop it. Automatically deleting
> > the references from all ACLs has not been
"Lee Wu" <[EMAIL PROTECTED]> writes:
> We noticed that we deleted /tmp/.s.PGSQL.5432 accidentally. However,
> anything seems fine.
> What is impact of removing it?
Anything that tries to connect to your postmaster via that socket will
fail. You might want to restart the postmaster to bring back
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> We are working on it, and hopefully in 8.1 you will be told where the
> user/group is referenced if you try to drop it. Automatically deleting
> the references from all ACLs has not been discussed but it's a possible
> outcome of the implementation.
[
On Fri, May 13, 2005 at 03:43:54PM -0500, Harris, Richard wrote:
Hi,
> I'm using PostgreSQL 8.0. I created a group called grpA and granted grpA
> 'SELECT' permission on view viewA. When I dropped grpA and created group
> grpB, group grpB 'automatically' has SELECT permission to viewA. After
> dro
Hi,
I'm using PostgreSQL 8.0. I created a group called grpA and granted grpA
'SELECT' permission on view viewA. When I dropped grpA and created group
grpB, group grpB 'automatically' has SELECT permission to viewA. After
dropping a group with permission to a view, I see that the permission
stored
Brandon Hines wrote:
Is there a method for killing a query from the server.
I have a number of users that manage to run queries that busy the server
preventing a number of critical queries from running within an
acceptable time limit.
I would like to kill off the queries that appear to be busyin
Hi,
We noticed that we deleted /tmp/.s.PGSQL.5432 accidentally. However, anything
seems fine.
Is this configurable?
What is impact of removing it?
Thanks,
Look in the HISTORY file in the tar ball.
On Fri, 2005-05-13 at 13:57, Kavan, Dan (IMS) wrote:
> I installed version 8.0.1 in feb/2005. There's no difference in the
> changelog between that version and 8.0.3.
>
>
>
>
> -Original Message-
> From: tom [mailto:[EMAIL PROTECTED]
> Sent
if i remember correctly, kill -TERM should do
it. you can get the pid of the query process by looking at pg_queries
table
Vikram
ps: be careful you dont kill -9 or some such.
On Fri, 13 May 2005, Brandon Hines wrote:
>
> Is there a method for killing a query from
I use kill -s SIGINT
Thanks,
Anjan
-Original Message-
From: Brandon Hines [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 2:32 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Killing a Query
Is there a method for killing a query from the server.
I have a number of users that
I installed version 8.0.1 in feb/2005. There's no difference in the
changelog between that version and 8.0.3.
-Original Message-
From: tom [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 2:26 PM
To: Kavan, Dan (IMS)
Subject: Re: [ADMIN] version 8.0.3
Kavan, Dan (IMS) wrote:
Is there a method for killing a query from the server.
I have a number of users that manage to run queries that busy the server
preventing a number of critical queries from running within an
acceptable time limit.
I would like to kill off the queries that appear to be busying the
server without
Hi all,
How do I figure out what's different in version 8.0.3 and how do I
upgrade on linux from v8.0.1 to v8.0.3?
Thanks,
~DjK
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Yes most of the data has type_code =2 probably 99.9%.
Thanks,
-Prasanth.
Tom Lane wrote:
> Prasanth <[EMAIL PROTECTED]> writes:
>
>>PG Version: 7.4.7
>
>
>>explain analyze select * from data where type_code >'2' AND type_code<'4';
>>[ is slow ]
>>explain analyze select * from data where type_c
Or,
Kill -s SIGINT
Thanks,
Anjan
-Original Message-
From: Gourish Singbal [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 9:27 AM
To: Ing. Jhon Carrillo
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] how do i kill user sessions?
you can try.
1) ps -ef | grep "postgres"
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Michael Kichanov)
would write:
> I wish to realize incremental backup, i.e. to dump only those tables
> which have changed from last backup.
>
> 1q. How i can solve this task with internal postgres tools?
> 2q. How I can to find out timest
you can try.
1) ps -ef | grep "postgres"
see which users are connectioned and than.
2) pkill -f 'postgres: postgres ';
its more safer i suppose than kill -9
regards
Gourish
On 5/12/05, Ing. Jhon Carrillo <[EMAIL PROTECTED]> wrote:
> I have a problem with the users administration. When I wa
Found the problem.
The Application opens the connections retrives the result set and does
processing on the data based on certian logic and than closes the
connections.
But during the time application does processing the connections are
open . thats the time i see 53 idle connections.
regards
Gou
Thank you much I will give it a try and see how it goes appreciate all the
info.
About ASCII to Unicode conversion (if you have only Latin1 characters in
the database):
Here is a receipt, how you can do a charset conversion from SQL_ASCII into
UNICODE on the Linux side:
(check these from manual
Hi All!
I wish to realize incremental backup, i.e. to dump only those tables
which have changed from last backup.
1q. How i can solve this task with internal postgres tools?
2q. How I can to find out timestamp of last change of the table?
Does anyone resolve this things?
Ps: postgres 7.3
Thanx
> > In file included from preproc.y:6409:
> > pgc.l: In function `yylex':
> > pgc.l:920: error: `xsoip' undeclared (first use in this function)
>
> Corrupted download maybe? That line refers to "xskip" not "xsoip".
>
Fine got a fresh download and got it through.
But does 8.0.x does not support
21 matches
Mail list logo
