it would appear my first mail didn't go thru
the basic gist was,
can anyone point out any caveats/pitfalls to the
postgresql inheritance functions..
On Tue, 19 Sep 2000, Jeff MacDonald wrote:
> i just found a (few) caveat already..
>
> 1:
>
> bignose=# create table people(
> bignose(# name
i just found a (few) caveat already..
1:
bignose=# create table people(
bignose(# name varchar(64),
bignose(# age int8,
bignose(# sin int4,
bignose(# id serial);
bignose=# create table soldier(
bignose(# rank varchar(32),
bignose(# post varchar(32)) inherits (people);
bignose=# alter table p
Doing the following:
create table test (f1 int);
create view v_test as select f1+1 as f11 from test;
drop table test;
then selecting from the view results in:
ERROR: Relation 'test' does not exist
which is fine.
Then I try:
create table test (f1 int);
select * from v
> So I still recommend that we remove the special value CURRENT. Then we
> can mark the datetime-related operators constant-foldable, which will
> eliminate a complaint that we can otherwise expect to hear constantly
> (saw another instance today in pgsql-sql).
OK.
- Thomas
At 10:42 19/09/00 +1000, Philip Warner wrote:
>At 11:37 18/09/00 -0400, Tom Lane wrote:
>>
>>The reason that changing pg_dump is a superior solution for this problem
>>is that there's only one place to change, not umpteen dozen ...
>>
>
>Well at least two, unless you like the following:
>
>zzz
At 11:37 18/09/00 -0400, Tom Lane wrote:
>
>The reason that changing pg_dump is a superior solution for this problem
>is that there's only one place to change, not umpteen dozen ...
>
Well at least two, unless you like the following:
zzz=# select * from pg_views;
ERROR: cache lookup of
At 11:37 18/09/00 -0400, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> writes:
>> FWIW, the patch below causes get_viewdef to produce:
>> ERROR: pg_get_viewdef: cache lookup of attribute 1 in relation 19136
>> failed for rule v_test
>> when a table has been deleted.
>
>Not much of a solu
Of course, if an alias for ichar is carried forward I
can write code for the current postgres that won't
break with future releases. I realize that I might end
up being the only person on the planet who ends up
using ichar, and that may not be sufficient
justification for an alias
Best,
Alex
I wrote:
> ichar() is for ODBC compliance. chr() could probably be an alias to it.
Ignore that. Probably "char()" had some parsing or overloading problems.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Maurizio writes:
> The only commad that I can execute is initdb.
>
> When I execute any other command I have a SIGSEGV error.
> Attached is a log file with the error.
I see no attachments to your post. You should look at the file
doc/FAQ_QNX4 if you haven't already. It seems that choosing a wo
Tom Lane writes:
> ichar(). Since that's part of the "oracle_compatibility" file,
> I'd assumed the function name spelling was the same as Oracle's.
> Not so?
ichar() is for ODBC compliance. chr() could probably be an alias to it.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org
Zeugswetter Andreas SB writes:
> Since you can write extensions to PostgreSQL that reach far into the OS,
> it does make sense to execute those extensions under a "non priviledged"
> user, and not postgres.
Agreed.
> This OS user would somehow be tied to the username that the client
> passes as
* Michael Meskes <[EMAIL PROTECTED]> [000918 05:03] wrote:
> If I change some stuff in a library that forces the user to recompile all
> programs because it's not binary compatible I have to change the major
> number right? But just changing the order in an enum datatype does not
> exactly look li
Hannu Krosing <[EMAIL PROTECTED]> writes:
>> Define your terms more carefully, please. What do you mean by
>> "unable to vacuum" --- what happens *exactly*?
> NOTICE: FlushRelationBuffers(access_right, 2009): block 1944 is
> referenced (private 0, global 2)
> FATAL 1: VACUUM (vc_repair_frag):
On Mon, 18 Sep 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > sounds good to me ... chr() == char(), I take it? is there a reason for
> > having both vs just changing char() to chr() in the odbc stuff?
>
> We don't control the ODBC specification ...
okay, granted, bu
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> sounds good to me ... chr() == char(), I take it? is there a reason for
> having both vs just changing char() to chr() in the odbc stuff?
We don't control the ODBC specification ...
regards, tom lane
On Mon, 18 Sep 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> >> I vote for just renaming it to chr(). Any objections?
>
> > first thing off the top of my head ... was there a reason why it was added
> > to contrib/odbc? ignoring the "oracle documentation", is it somet
PgSQL, Inc just recently announced that they were working on this ... I
haven't heard of anyone else, but that doesn't mean nobody else is ...
On Mon, 18 Sep 2000, Dan Browning wrote:
> I'm developing a db-driven web site for a client.
> So far the solution happens to use a lot of open source
I'm developing a db-driven web site for a client.
So far the solution happens to use a lot of open sources software (best tool
for the job).
But when looking at areas of high-availability and performance in relation
to our database back-end, I'm trying to find a solution that will fit the
clients
"g.p.ciceri" <[EMAIL PROTECTED]> writes:
> gcc -c -I../../src/include -O2 -Wall -Wmissing-prototypes
> -Wmissing-declarations -I. -fpic soundex.c -o soundex.o
> soundex.c: In function `text_soundex':
> soundex.c:37: invalid lvalue in assignment
> make: *** [soundex.o] Error 1
> perhaps the inte
The Hermit Hacker <[EMAIL PROTECTED]> writes:
>> I vote for just renaming it to chr(). Any objections?
> first thing off the top of my head ... was there a reason why it was added
> to contrib/odbc? ignoring the "oracle documentation", is it something
> that is/was needed for ODBC?
Now that I
> Hi,
> I'm just curious how MVCC will work witk WAL ? Will
> it work in the same fashion as now only tuples written
> using WAL ?
Yes.
> Or will it search for old tuple's versions in log ?
SMGR is strill non-overwriting one.
Vadim
On Mon, 18 Sep 2000, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > Not documented (from oracle_compat.c) in PG documentation:
> > btrim()
> > ascii()
> > ichar()
> > repeat()
> > and about ichar() is nothing in Oracle documentation, it's knows chr()
> > only...
>
Philip Warner <[EMAIL PROTECTED]> writes:
> FWIW, the patch below causes get_viewdef to produce:
> ERROR: pg_get_viewdef: cache lookup of attribute 1 in relation 19136
> failed for rule v_test
> when a table has been deleted.
Not much of a solution --- or do you propose to go through and hac
Karel Zak <[EMAIL PROTECTED]> writes:
> Not documented (from oracle_compat.c) in PG documentation:
> btrim()
> ascii()
> ichar()
> repeat()
> and about ichar() is nothing in Oracle documentation, it's knows chr()
> only...
Sounds to me like calling it ichar() was an err
Hi all,
I've just downloaded the latest CVS snapshot, to play with
TOASTed text field. I've tried to compile contrib extensions
but I've some problem with soundex.
I take
gcc -c -I../../src/include -O2 -Wall -Wmissing-prototypes
-Wmissing-declarations -I. -fpic soundex.c -o soundex.o
soundex.c
If I change some stuff in a library that forces the user to recompile all
programs because it's not binary compatible I have to change the major
number right? But just changing the order in an enum datatype does not
exactly look like such a big change. But the only way to avoid this problem
is add
When you use 'make distclean' make is under control of the
Makefile and does exactly what the code writer wants, which usually is to
rm all .o files.
On Mon, 18 Sep 2000, Michael Meskes wrote:
> On Sun, Sep 17, 2000 at 12:29:16PM +0200, Peter Eisentraut wrote:
> > It might be that `mak
At 16:29 17/09/00 -0400, Tom Lane wrote:
>
>create table test (f1 int);
>create view v_test as select f1+1 as f11 from test;
>drop table test;
>
>then run pg_dump:
>
>getTables(): SELECT failed. Explanation from backend: 'ERROR: cache
lookup of attribute 1 in relation 400384 failed
>'.
>
FWIW,
On Sun, Sep 17, 2000 at 12:29:16PM +0200, Peter Eisentraut wrote:
> It might be that `make depend' is broken in one way or another. What you
> want to do is rm `find . -name depend` and then ./configure
> --enable-depend. Or you could try to rerun make depend then. I have a
> feeling what is causi
Hi,
I'm just curious how MVCC will work witk WAL ? Will
it work in the same fashion as now only tuples written
using WAL ?
Or will it search for old tuple's versions in log ?
thanks devik
Tom Lane wrote:
>
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > I get the following on untuned Linux (Redhat 6.2) using stock 7.0.2
> > rpm-s
>
> > NOTICE: RegisterSharedInvalid: SI buffer overflow
> > NOTICE: InvalidateSharedInvalid: cache state reset
>
> > Actually I get many of them ;(
>
Tom Lane writes:
> Well, we could fix it either by propagating use of "unsigned char" all
> over the place, or by casting the arguments given to ctype macros.
> The former would be a lot more invasive because it would propagate to
> routines that don't actually call any ctype macros (since they'd
At 19:05 18/09/00 +1000, Philip Warner wrote:
>
>I guess an alternative would be to define a special 'iscacheable' function:
>eg.
>
> function constant(arg ) returns
>
>so we could have:
>
>field < constant(current_timestamp - interval '1 hour')
>
>although this looks suspiciously like an o
At 16:37 11/09/00 +, Thomas Lockhart wrote:
>> AFAIK hardly anyone actually uses CURRENT, and I've been thinking of
>> proposing that we eliminate it to make the world safe for constant-
>> folding timestamp operations. (Thomas, any comments here?)
>
>Well, it is a feature from "the old days"
> But the pg_shadow authentication is based on credentials
> provided by the
> client whereas what you propose here would run on the server, so this
> doesn't make sense.
Since you can write extensions to PostgreSQL that reach far into the OS,
it does make sense to execute those extensions und
> > add the functionality for "with check option" clause of
> create view
> >
>
> I'm not familiar with this. What does it do?
It checks on view insert or update, that the resulting tuple will still
be seen through this view (it satisfies the view's where restriction).
If not, the insert
On Fri, Sep 15, 2000 at 10:24:30AM -0400, Tom Lane wrote:
> I'd suggest a full "make distclean" and reconfigure. Looks like you
I did. And I did it more than just once but to no avail.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
On Fri, Sep 15, 2000 at 10:23:01AM -0400, Tom Lane wrote:
> They are fixed in any one version, and really are not very likely to
> change across versions either. But I suppose it could happen.
That's good enough for my usage I think.
> Exactly how "hard coded" do you mean? If you #include "cat
39 matches
Mail list logo
