I just noticed the following peculiar behavior.
By default, a table's owner has all access rights for it:
play=> create table foo(f1 int);
CREATE
play=> insert into foo values(1);
INSERT 328713 1
But let him grant some rights to someone else:
play=> gran
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > My proposal is to set includedir=${prefix}/include/postgresql (instead of
> > ${prefix}/include) in such cases where the prefix is shared, i.e., it does
> > not contain something like "pgsql" already. (precise pattern t.b.d.)
> H
anybody knows to use pqaccess ?
I would like ->
table : ___
f1 : ___
execute the query : SELECT f1, f2, f3,f4 FROM 'name_table' WHERE f1 LIKE
'name_f1' ORDER BY f1 ;
|--|--|-|---|
| f1 |f2|f3 | f4 |
|
Philip Warner <[EMAIL PROTECTED]> writes:
> This would be something I'd like to do as a learning exercise. However,
> aren't we 2 days from beta? Is this enough time to learn how to add a
> function to the backend?
In practice, you've probably got a week. I believe Marc is planning to
be out of
At 11:17 28/09/00 -0400, Tom Lane wrote:
>
>Hmm, good point. There isn't any real easy way to refer to a sequence
>by OID --- the sequence functions only accept names --- but I suppose
>someone out there might be doing something with sequence OIDs.
So long as the backend & metadata don't rely on
Philip Warner <[EMAIL PROTECTED]> writes:
> At 11:01 28/09/00 -0400, Tom Lane wrote:
>> A data-only reload
>> would fail to make that guarantee unless you drop and recreate
>> the sequence.
> Will this cause problems in an existing database because the sequence OID
> changes?
Hmm, good point. T
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I suppose there isn't any good reason that elog.c and exc.c refer to
> sys_nerr and sys_errlist directly rather than using strerror()
I don't see any direct references to sys_errlist. The references to
sys_nerr are necessary to avoid coredump with a
At 11:01 28/09/00 -0400, Tom Lane wrote:
>A data-only reload
>would fail to make that guarantee unless you drop and recreate
>the sequence.
Will this cause problems in an existing database because the sequence OID
changes?
Philip
Philip Warner <[EMAIL PROTECTED]> writes:
> OK. Given the discussion of 'select nextval', do you know if 'select
> setval' will set the is_called flag?
Looks like it does, both by experiment and by reading the code.
So if you issue a setval() you don't need a nextval() as well.
However you still
At 10:36 28/09/00 -0400, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> writes:
>> My inclinations is do do the following:
>
>> - Issue 'CREATE SEQUENCE...Initial Value 1...' in OID order
>> - Issue 'SELECT SETVAL...' at end of data load.
>
>Seems reasonable, except you should not necessarily
Philip Warner <[EMAIL PROTECTED]> writes:
> My inclinations is do do the following:
> - Issue 'CREATE SEQUENCE...Initial Value 1...' in OID order
> - Issue 'SELECT SETVAL...' at end of data load.
> This means that a schema-only restore will hgave all sequences set up with
> initial value = 1, an
I suppose there isn't any good reason that elog.c and exc.c refer to
sys_nerr and sys_errlist directly rather than using strerror() (probably
an artifact from before port/strerror.c was added?) and given that it is
provably unportable to do so (Cygwin) I'm inclined to make the obvious
fix.
--
Pe
Tom Lane writes:
> Hmm, so basically you propose an install setup whereby 'bin' and 'lib'
> files can go directly into /usr/local/bin and /usr/local/lib, but
> everything else still lives in postgres-specific directories?
Yes.
In detail, for those who cry "do it like Debian", we have these cate
> > The it will be MUCH faster to create secondary index which
> > is much smaller than heap and use values from it.
>
> Agreed. But this will add 16 bytes (2 xid + 2 cid) to size of btitems.
> Currently, total size of btitem for 2-int4 key index is 16 bytes =>
> new feature will double size of i
> > question is whether we need it for hash indices. it is definitely
> > good for btree as they support range retrieval. hash ind. doesn't
> > it so I wouldn't implement it for them.
>
> We need in fast heap tuple --> index tuple lookup for overwriting
> storage manager anyway...
oh .. there w
Tom Lane writes:
> OK. BTW, what is the status of the changeover you proposed re using
> OIDs instead of int4 userids as the unique identifiers for users?
Because of the pg_dumpall thing that had to be postponed for another
release, otherwise the users would be associated to the wrong groups on
The Hermit Hacker writes:
> Pointers to what this is? Do we have it documented anywhere? Search
> engine, of course, is done, so can't search there ...
>From experience, not from code knowledge, this happens when some backend
crashed and took the others with it and the postmaster is _recoverin
It recently came to my attention that pg_dump dumps 'CREATE SEQUENCE' and
'SELECT NEXTVAL' commands for both data-only and schema-only output. This
results in problems for users who do the two in separate steps, and seems a
little odd.
Also, I'd be interested to know what the purpose of 'SELECT
18 matches
Mail list logo
