DROP AGGREGATE(7) SQL Commands DROP AGGREGATE(7)NAME
DROP AGGREGATE - remove a user-defined aggregate function
SYNOPSIS
DROP AGGREGATE name ( type ) [ CASCADE | RESTRICT ]
INPUTS
name The name (optionally schema-qualified) of an existing aggregate function.
type The input data type of the aggregate function, or * if the function accepts any input type. (Refer to the PostgreSQL User's Guide
for further information about data types.) [Comment: This should become a cross-reference rather than a hard-coded chapter number]
CASCADE
Automatically drop objects that depend on the aggregate.
RESTRICT
Refuse to drop the aggregate if there are any dependent objects. This is the default.
OUTPUTS
DROP AGGREGATE
Message returned if the command is successful.
ERROR: RemoveAggregate: aggregate 'name' for type type does not exist
This message occurs if the aggregate function specified does not exist in the database.
DESCRIPTION
DROP AGGREGATE will delete an existing aggregate definition. To execute this command the current user must be the owner of the aggregate.
NOTES
Use CREATE AGGREGATE [create_aggregate(7)] to create aggregate functions.
USAGE
To remove the myavg aggregate for type int4:
DROP AGGREGATE myavg(int4);
COMPATIBILITY
SQL92
There is no DROP AGGREGATE statement in SQL92; the statement is a PostgreSQL language extension.
SQL - Language Statements 2002-11-22 DROP AGGREGATE(7)
Check Out this Related Man Page
ALTER AGGREGATE(7) PostgreSQL 9.2.7 Documentation ALTER AGGREGATE(7)NAME
ALTER_AGGREGATE - change the definition of an aggregate function
SYNOPSIS
ALTER AGGREGATE name ( argtype [ , ... ] ) RENAME TO new_name
ALTER AGGREGATE name ( argtype [ , ... ] ) OWNER TO new_owner
ALTER AGGREGATE name ( argtype [ , ... ] ) SET SCHEMA new_schema
DESCRIPTION
ALTER AGGREGATE changes the definition of an aggregate function.
You must own the aggregate function to use ALTER AGGREGATE. To change the schema of an aggregate function, you must also have CREATE
privilege on the new schema. To alter the owner, you must also be a direct or indirect member of the new owning role, and that role must
have CREATE privilege on the aggregate function's schema. (These restrictions enforce that altering the owner doesn't do anything you
couldn't do by dropping and recreating the aggregate function. However, a superuser can alter ownership of any aggregate function anyway.)
PARAMETERS
name
The name (optionally schema-qualified) of an existing aggregate function.
argtype
An input data type on which the aggregate function operates. To reference a zero-argument aggregate function, write * in place of the
list of input data types.
new_name
The new name of the aggregate function.
new_owner
The new owner of the aggregate function.
new_schema
The new schema for the aggregate function.
EXAMPLES
To rename the aggregate function myavg for type integer to my_average:
ALTER AGGREGATE myavg(integer) RENAME TO my_average;
To change the owner of the aggregate function myavg for type integer to joe:
ALTER AGGREGATE myavg(integer) OWNER TO joe;
To move the aggregate function myavg for type integer into schema myschema:
ALTER AGGREGATE myavg(integer) SET SCHEMA myschema;
COMPATIBILITY
There is no ALTER AGGREGATE statement in the SQL standard.
SEE ALSO
CREATE AGGREGATE (CREATE_AGGREGATE(7)), DROP AGGREGATE (DROP_AGGREGATE(7))
PostgreSQL 9.2.7 2014-02-17 ALTER AGGREGATE(7)
Hy all,
I have a problem...can some one help me...
I have a file of records sort:
30|239|ORD|447702936929 |blackberry.net |20080728|141304|00000900|2|0000000000000536|28181|0000000006|0000000001|10|1
30|239|ORD|447702936929 |blackberry.net ... (4 Replies)
How can I check and see if the first parameter is a file existing in the current path or it is a real file and user input some random name in an IF statement? (5 Replies)