The cost of preventing every stupid database use is too high.
--
thanks it answers my concern. many a times we face the same
situation with the marketing people of our company. the complexity
of stopping stupid usage can be quite non trivial at times.
regds
mallah.
-
Em Dom, 2006-12-10 às 00:47 +0530, Rajesh Kumar Mallah escreveu:
> psql> CREATE INDEX x on test (col1);
> psql> CREATE INDEX y on test (col1);
>
> What is (are) the downsides of disallowing the
> second index. which is *exactly* same as
> previous?
What if PostgreSQL make a NOTICE about this? The
On 12/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Rajesh Kumar Mallah" <[EMAIL PROTECTED]> writes:
> Suppose an index get corrupted. And you need create a new index
> with exact specs and then drop the old index. Is it better to
> have a performing corrupted index or not have it at all and tempora
"Rajesh Kumar Mallah" <[EMAIL PROTECTED]> writes:
> Suppose an index get corrupted. And you need create a new index
> with exact specs and then drop the old index. Is it better to
> have a performing corrupted index or not have it at all and temporarily
> suffer some performance degradation ?
The
Sir,
Suppose an index get corrupted. And you need create a new index
with exact specs and then drop the old index. Is it better to
have a performing corrupted index or not have it at all and temporarily
suffer some performance degradation ?
that was one scenerio which comes to my mind for having
On 12/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Rajesh Kumar Mallah" <[EMAIL PROTECTED]> writes:
> Some of our tables have duplicate indexes on same column by different
> index names.
> Should the database server check for the existance of (effectively)
> same index in
> a table before creating
"Rajesh Kumar Mallah" <[EMAIL PROTECTED]> writes:
> Some of our tables have duplicate indexes on same column by different
> index names.
> Should the database server check for the existance of (effectively)
> same index in
> a table before creating a new one.
I'd vote not; I think this would get
Hi,
Some of our tables have duplicate indexes on same column by different
index names.
Should the database server check for the existance of (effectively)
same index in
a table before creating a new one.
Regds
Mallah.
---(end of broadcast)---
TIP
