Peter Eisentraut wrote:
>
> Kevin O'Gorman writes:
>
> > 2) Because _something_ was made for Perl, the 'make install'
> > has to be root. Okay. But this is leaving some stuff behind
> > that is owned by root. When I attempt a subsequent
> > &
ouble, and have
to delete these things manually.
These events are illustrated in an script(1) capture file,
which I have edited down to a version I have attached here.
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'
Tom asked me to bust it some more 8-)
I've attached the query and the gdb backtrace. This is very
repeatable, so if there's more info needed, let me know.
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'[EMAIL
ecause the directory is not empty), and
it goes okay.
I've attached a capture of the initdb run. There's not much to
go on there....
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'[EMAIL PROTECTED]
At school: mail
the backend?
Or am I just going at this all wrong in some way?
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'[EMAIL PROTECTED]
At school: mailto:[EMAIL PROTECTED]
Web: http://www.cs.ucsb.edu/~kogorman/index.html
Web:
ing myself in the foot, I would like to
educate myself about how they work inside the current code. Does
anyone know where best to look? It can be the code, better if it's
a document. I'm happy to RTFM or RTFC, but I'd like to know where
to start.
++ kevin
--
Kevin O'
re general treatment of
parentheses later.
What do you think?
++ kevin
On Sun, 29 Oct 2000, Kevin O'Gorman wrote:
>
> That was very helpful. And I was able to eliminate most of the
> remaining restrictions by letting a SelectStmt be EITHER
> a) a simple_select (which has
:
> >> Applied. Thanks.
>
> Itchy trigger finger today, Bruce?
>
> Please revert the change --- I'm still discussing it with Kevin offlist,
> but I don't feel it's acceptable as-is because it breaks reasonable
> (non-redundant) UNION/INTERSECT/EXCEPT co
opos of another comment you made, when we decide how it's going
to be, we should have a bunch more things put in the regression tests,
not just UNIONs, to make sure it doesn't change unnoticed.
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwa
g at this stuff. Is it stable enough to install and run
now?
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'[EMAIL PROTECTED]
At school: mailto:[EMAIL PROTECTED]
Web: http://www.cs.ucsb.edu/~kogorman/index.html
Web: ht
the one in parentheses. In this version of
gram.y, the square bracket form treats SELECT statements the same
as the other allowed statements. As discussed before on this list,
psql cannot make sense out of the results of such a thing, but an
application might. And I have designs on just such an
Kevin O'Gorman wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> > Anyway, the bottom line of all this rambling is that if you can get
> > rid of the distinction between SelectStmt and select_claus
[EMAIL PROTECTED] wrote:
>
> "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> Anyway, the bottom line of all this rambling is that if you can get
> rid of the distinction between SelectStmt and select_clause altogether,
> that would be fine with me. You might c
.
Given a target syntax (like from the SQL standard) this
can be done in a day or so. The question is: should it
happen, and if so what is the target syntax?
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'[EMAIL PROTE
t; ((select * from foo) union (select * from bar));
> but not this:
> select * from foo where exists
> ((select * from foo) union ((select * from bar)));
> ERROR: parser: parse error at or near ")"
>
> If there are any yacc hackers out
7;t the error message give more info about the table involved?
It's kinda hard to pick out the culprit from a 3GB script.
3) I'm confused: is "PUBLIC" different from "world"?
I'm sorry I can't dive in and show how to fix these things;
it's my
Tom Lane wrote:
>
> "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> > It's odd. I had already tried "8 Oct 2000 10:00:00 PDT" on one system
> > (RedHat Linux 6.1), and it had worked. Today I'm building on a
> > Caldera 2.3 system
Tom Lane wrote:
>
> "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> > so I tried going back to '7 Oct 2000 10:00:00 PST' and it's better,
> > but regression tests fail on the rule system. It makes the server
> > die. Since rules are
guessing that no multibyte means I'm locked in
US-ASCII. In any event, this seems an unnecessary gotcha
for the inexperienced, and it may mean that I'm locked into
multibyte suppport that I don't want or need.
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Perm
I've just built 7.1 from a slightly old point in the tree:
October 9. Regression tests pass, but postmaster won't
start.
I'm getting a complaint from pg_ctl that it cannot find
postmaster.opts.default.
What am I missing?
++ kevin
--
Kevin O'Gorman (805) 650-6274 mai
7;m not familiar enough with CVS or your changelog system
well enough
to know a good way to find a time-point that might be stable
enough
for me. How would I find out where I need to be??
++ kevin
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder:
m
Sorry to bother you all. I got more recent docs and
found I needed a different command to do this, and
it works.
++ kevin
Kevin O'Gorman wrote:
>
> I've been unable to follow the directions
> in the Programmer's Guide
> for getting to the anonymous CVS server.
I've been unable to follow the directions
in the Programmer's Guide
for getting to the anonymous CVS server.
I'm running RedHat 6.1, and CVS 1.10 which
comes with it. I get as far as entering
the 'postgresql' password, but it gets
rejected every time.
Any hints?
++
Tom Lane wrote:
>
> "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> > I suggest that the CREATE RULE syntax be relaxed so that
> > it is legal to have a list of SELECT commands in a rule.
>
> I don't have any strong objection to this myself, but
I said it's only 2
lines.
++ kevin
---
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder:
mailto:Kevin.O'[EMAIL PROTECTED]
At school: mailto:[EMAIL PROTECTED]
Web: http://www.cs.ucsb.edu/~kogorman/index.html
Web: http://trixie.kosman.via.ayuda.co
ne listed. Is there
something
about executing a list I don't know about, or is this also
old news??
++ kevin
Tom Lane wrote:
>
> "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> > If I define two rules for the same action, each with
> > a single select c
d2 (cost=0.00..20.00 rows=1000
width=4)
EXPLAIN
--
Kevin O'Gorman (805) 650-6274 mailto:[EMAIL PROTECTED]
Permanent e-mail forwarder: mailto:Kevin.O'[EMAIL PROTECTED]
At school: mailto:[EMAIL PROTECTED]
Web: http://www.cs.ucsb.edu/~kogorman/index.html
Web
27 matches
Mail list logo
