I think somebody has the "owner" address forwarding to the list.
Really annoying. Would somebody please stop that?
Thanks,
-Roberto
- Forwarded message from [EMAIL PROTECTED] -
From: [EMAIL PROTECTED]
Subject: Majordomo Delivery Error
To: [EMAIL PROTECTED]
X-VMS
At 21:00 31/03/01 -0500, Tom Lane wrote:
>
>If we change the code again based on the latest discussion, then pg_dump
>would have to detect whether there are conflicting defaults, which would
>mean looking at all the parents not just the rightmost one. Ugh. That
>might be a good reason not to cha
Hi Everybody:
How can
i set permission for any user (in a database) in the entire database (all
tables) ??? with GRANT is just one table (or list), but i want , for
example, create a user and set his permissions in all tables , but just SELECT
for example, (without set sup
At 20:25 31/03/01 -0500, Tom Lane wrote:
>
>> That's what I meant; can we easily do the 'not in the parent' part, since
>> we may have to go up a long hierarchy to find the parent?
>
>pg_dump must already contain code to traverse the inheritance hierarchy
>(I haven't looked to see where). Couldn'
On Fri, Mar 30, 2001 at 12:10:59PM -0500, Tom Lane wrote:
> Comments? I'm going to implement and commit this today unless I hear
> loud squawks ...
I like it in general and I think it opens some interesting
possibilities. I don't know much about how the inheritance system is
implemented, so I w
Well, once I figured out a few things about how to use the Unix part
of MacOS X it seemed to work without a hitch in the regression
testing. I need to figure out how to make the system start it up
automatically at boot time still, but then I need to figure out how
to do double sided printing
At 20:40 31/03/01 -0500, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> writes:
>> You are correct; flagInhAttrs in common.c does the work, and it should be
>> easy to change. At the moment it extracts all tables attrs then looks for
>> an attr with the same name in any parent table. We can ex
Philip Warner <[EMAIL PROTECTED]> writes:
> Looks like it; and just to confirm, based on previous messages, I assume I
> should look at the parents from right to left?
At the moment that would be the right thing to do.
If we change the code again based on the latest discussion, then pg_dump
woul
On Fri, Mar 30, 2001 at 10:48:54AM -0500, Bruce Momjian wrote:
> > Bruce Momjian writes:
> >
> > > I have started coding a user/group administration tool that allows you
> > > to add/modify/delete users and groups. I should have something working
> > > in a week. I will look similar to my pgmon
I just built and tested RC1 on Linux 2.4.2, with glibc-2.2.2 and
gcc-2.95.2 on a Debian 2.2+ x86 system. ("+" implying some packages
from "unstable".)
I configured it --with-perl --with-openssl --with-CXX.
It built without errors, but with a few warnings.
This one seemed (portably) odd:
--
On Thursday 29 March 2001 22:15, Tom Lane wrote:
> > Just looked in heapam.c - I can fix it in two hours.
> > The question is - should we do this now?
>
> This scares the hell out of me.
>
> I do NOT think we should be making quick-hack changes in fundamental
> system semantics at this point of th
Philip Warner <[EMAIL PROTECTED]> writes:
> You are correct; flagInhAttrs in common.c does the work, and it should be
> easy to change. At the moment it extracts all tables attrs then looks for
> an attr with the same name in any parent table. We can extend this to check
> NOT NULL and DEFAULT. Sh
Philip Warner <[EMAIL PROTECTED]> writes:
> At 20:02 31/03/01 -0500, Tom Lane wrote:
>> Perhaps we should just hack that code
>> to not suppress inherited attrs when they have default values and/or
>> NOT NULL that's not in the parent.
> That's what I meant; can we easily do the 'not in the paren
At 20:02 31/03/01 -0500, Tom Lane wrote:
>
>Perhaps we should just hack that code
>to not suppress inherited attrs when they have default values and/or
>NOT NULL that's not in the parent.
That's what I meant; can we easily do the 'not in the parent' part, since
we may have to go up a long hierarc
Philip Warner <[EMAIL PROTECTED]> writes:
> At 01:36 31/03/01 -0500, Tom Lane wrote:
>> which is OK as far as the field set goes, but it loses the additional
>> DEFAULT and NOT NULL information for the child table. Any thoughts on
>> the best way to fix this?
> Can pg_dump easily detect overridd
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > First, here is a patch which will prevent this from happening in the
> > future. Do people want this held for 7.2 or applied now? It disables
> > the creation of user indexes on system tables.
>
> > + if (heapRelationName && !allow_system_tabl
Bruce Momjian <[EMAIL PROTECTED]> writes:
> First, here is a patch which will prevent this from happening in the
> future. Do people want this held for 7.2 or applied now? It disables
> the creation of user indexes on system tables.
> + if (heapRelationName && !allow_system_table_mods &&
[EMAIL PROTECTED] (Nathan Myers) writes:
>> This seems pretty random. It would be more reasonable if multiple
>> (default) inheritance weren't allowed unless you explicitly specify a new
>> default for the new column, but we don't have a syntax for this.
> I agree, but I thought the original iss
[EMAIL PROTECTED] (Nathan Myers) writes:
> Of course PG is different from any O-O language. I don't know if PG
> has an equivalent to the "base-class context". I suppose PG has a long
> history of merging like-named members, and that the issue is just of
> the details of how the merge happens
Can I get a comment on this patch. Hold for 7.2 or apply?
initdb works with the patch. People who create indexes on global tables
get a failed database, while people who create indexes on non-global
system tables get unreliable indexes. This prevents such index
creation.
I don't know how man
Bruce Momjian <[EMAIL PROTECTED]> writes:
> test=> CREATE UNIQUE INDEX shadow_index ON pg_shadow (usename);
> CREATE
> test=> select * from pg_shadow;
> ERROR: Index 'pg_shadow_sysid_index' does not exist
> test=> \q
> $ psql test
> psql: FATAL 1: Index
Hi EveryBody
When i connect to my database in windows98 (ODBC) to the
server in Linux, i can execute SELECT staments , but no INSERT or UPDATE
staments... the error 'Key Violation ..Connection is readonly , only select
staments are allowed' appears. the user was created wit
Hi EveryBody!!!
How can i set permission for any
user (SELECT for example) in all tables (any database) without list all tables
in GRANT stament?
Thanks!
Hi EveryBody:
How can i get the structure of a
table (Fields names, data types, etc)???
Thanks
Hi,
I'm in search of a hack that will allow me to clear the on-row commit
status bits. Any assistance would greatly be appreciated.
Thanks,
Dave Perkins
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister com
I have added the recent elog and internationalization email thread to
TODO.detail. (Wow, I spelled internationalization right the first
time.)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard dri
Strange. The compiler work with all my old project and also with the old
version of postgresql.
However I will search the problem and I will post the risult.
Maurizio
.
- Original Message -
From: "Peter Eisentraut" <[EMAIL PROTECTED]>
To: "Maurizio" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTE
At 15:49 31/03/01 +1000, Philip Warner wrote:
>
>(I *think* that's right...).
>
I've sent a version of this to patches. I have verified it dumps & restores
the regression db, excluding the f_star data, which is I *hope* a the one
acceptable failing of pg_dump (ie. reordered attrs in tables).
--
28 matches
Mail list logo
