Hello Postgressers,
I am using table inheritance and have e.g. the following tables:
create table animal ( ... );
create table dog ( ... ) inherits (animal);
create table cat ( ... ) inherits (animal);
create table person ( ... ) inherits (animal);
create table musician ( ...
> regression=# create index mv1 on t1 (f1);
...
> ERROR: materialized view "mv1" already exists
Is in fact the one I prefer ;^)
I come from a DBMS world where Tables and Indexes do not share the same name
space,
and have to change my mind !
Thanks you Tom for pointing that.
Regards
PAscal
On Sun, Mar 4, 2018 at 11:22:56PM -0800, Igal wrote:
>
>
> On 03/04/2018 09:57 PM, Tom Lane wrote:
> >Igal writes:
> >>On 03/04/2018 07:24 PM, Adrian Klaver wrote:
> >>>On 03/04/2018 05:53 PM, Igal wrote:
> I am trying to connect to http://momjian.us/ but I get connection
> timeout (fro
legrand legrand writes:
> I thougth that thoses messages where using relation's relkind:
> ..
> wouldn't it be easier to read for beginners ?
I doubt it would be an improvement. Consider this example:
regression=# create table t1 (f1 int);
CREATE TABLE
regression=# create materialized view mv1
OK, that noted !
thank you for the quick answers
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On Sat, Mar 10, 2018 at 10:54 AM, legrand legrand <
legrand_legr...@hotmail.com> wrote:
> I thougth that thoses messages where using relation's relkind:
> r = ordinary table,
> i = index,
> S = sequence,
> t = TOAST table,
> v = view,
> m = materialized view,
> c = composite type,
>
I thougth that thoses messages where using relation's relkind:
r = ordinary table,
i = index,
S = sequence,
t = TOAST table,
v = view,
m = materialized view,
c = composite type,
f = foreign table,
p = partitioned table
wouldn't it be easier to read for beginners ?
Regard
On 03/10/2018 07:00 AM, legrand legrand wrote:
Hello,
When trying to create an already existing index (in pg 9.5)
SQL> create index if not exists NEWINDEX on SCHEMA.TABLE(COL);
> relation "NEWINDEX" already exists, skipping
message speaks about relation (and not index)
https://www.pos
Hello,
When trying to create an already existing index (in pg 9.5)
SQL> create index if not exists NEWINDEX on SCHEMA.TABLE(COL);
> relation "NEWINDEX" already exists, skipping
message speaks about relation (and not index)
Would it be possible that this message reports the correct object
On Sat, Mar 10, 2018 at 3:50 PM, Adrian Klaver
wrote:
> On 03/09/2018 10:49 PM, amitabh kumar wrote:
>
>> We have multiple servers with PG versions in 8.4, 9.2, 9.3, 9.4 and 9.5,
>> that we want to upgrade to 9.6. We want to be sure that all applications
>> will run smoothly after upgrade.
>>
>
>
On 03/09/2018 10:49 PM, amitabh kumar wrote:
Hi,
I would like to know about application dependency of PostgreSQL version
upgrade.
We have multiple servers with PG versions in 8.4, 9.2, 9.3, 9.4 and 9.5,
that we want to upgrade to 9.6. We want to be sure that all applications
will run smooth
11 matches
Mail list logo
