From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Campbell, Lance" <lance(at)uiuc(dot)edu> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Terminology Question |
Date: | 2007-08-20 14:50:18 |
Message-ID: | dcc563d10708200750g593cd883v60b71e045e1c91a8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 8/20/07, Campbell, Lance <lance(at)uiuc(dot)edu> wrote:
>
> Terminology Question:
>
> If I use the following statement:
>
> I am backing up schema XYZ every 30 minutes.
>
> Does this statement imply that I am only backing up the definition of the
> data? Or does it mean that I am backing up the definition of the data and
> the data within the schema object?
In db parlance, schema means two different things really.
One is that layout of your data (how tables are related etc...)
The other is the namespace that a set of objects can live in. i.e.
There is a certain amount of overlap here as well.
dbname.schemaname.objectname.fieldname
In this instance, "backing up" a schema pretty much implies the
namespace version of schema.
OTOH, a phrase like "I think your schema has some design flaws pretty
obviously points to the first definition relating to the layout of
your data.
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-08-20 17:55:15 | Re: Terminology Question |
Previous Message | Campbell, Lance | 2007-08-20 14:36:00 | Terminology Question |