On Sat, 9 Aug 2003, Larry Rosenman wrote:
> I tried(!) to load my 7.3.4 data into 7.4CVS.
>
> the Bricolage folks have managed to make a circular definition (at least
> not loadable).
>
> why does each setval() call invoke the pager?
>
> the dump I used is at:
>
> http://www.lerctr.org/~ler/pg.du
SuSE 7.3, PostgreSQL cvshead (7.4)
This is as far as I've gotten with 7.4.
It is built and configured like my 7.3 installation
on the same machine. I have built from CVS previously.
And the production sources always builds very nice and clean.
Nothing runs. gbd output is below. It is balking
On Sat, 09 Aug 2003 21:17:05 -0400
Tom Lane <[EMAIL PROTECTED]> said something like:
>
> Could you supply the relation names corresponding to the relation OIDs
> appearing in pg_locks, so we can be sure who's processing what?
>
Sure, if you tell me how ;-) I looked at the view definition and t
Tom Lane wrote:
> Joe Conway <[EMAIL PROTECTED]> writes:
> > This one I don't understand:
> > o Support construction of array result values in expressions
>
> Not sure why you don't understand it, when you did it ;-). It's asking
> for the ARRAY[] syntax. Bruce, that one should be marked done.
Title: Farewell
It's
time for formal acknowledgement that I'm not in The Project any
more.
I'm not interested in small features/fixes and have
no time for big ones.
It was this way for very long time and I don't see
how/when that could change.
My participation in The Project was one of t
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> What's the point of running a regression tests if it's going to
> use the old binary?
It doesn't, ordinarily. Feel free to trace through the scripts and
find out what went wrong.
regards, tom lane
---(end
Bruce Momjian wrote:
o Add PL/PgSQL PROCEDURES that can return multiple values
Do you have TODO to add for this? I removed the original one because,
as worded, it was complete.
Actually, now that I look at it again, it is referring to procedures,
not functions. Maybe just make it:
o Add c
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> On Thu, Aug 07, 2003 at 05:20:58PM +0200, [EMAIL PROTECTED] wrote:
>> I have NI_NUMERICHOST defined in netdb.h
> That's for getnameinfo(). getnameinfo() is older than
> getaddrinfo() ...
> If you have that, I assume you have AI_NUMERICHOST in the same
>
On Mon, Aug 11, 2003 at 09:40:25AM +0800, Christopher Kings-Lynne wrote:
> Has anyone reviewed the compatibility list for 7.4 yet?
> I seem to remember something about us having the unique predicate now or
> something?
I hacked up a really simplistic implementation of it, but it wasn't
included i
Larry Rosenman wrote:
> As soon as a beta tarball shows up, I'll cut changes for UnixWare for
> --enable-threads,
> and also to do -D_REENTRANT anyway on UnixWare.
OK.
> What about Kean's change to allow absolute DT_SONAME's?
>
> Can that get applied, and used for SCO and UnixWare?
Can you ver
I've not been keeping up with the thread re who has what version of
getpwuid_r... But just to clarify things the "right" version is:
int getpwuid_r(uid_t uid, struct passwd *pwd, char *buffer,
size_t bufsize, struct passwd **result);
documented at:
http://www.opengroup.org/onl
Hi,
I dropped the owner of a table (with no complaints), and now I get this:
psql:
asdf=# \dt
List of relations
Schema | Name | Type | Owner
+--+---+
public | a1 | table |
pg_dump:
pg_dump: WARNING: owner of data type "a1" appears to be invalid
pg_du
Neil Conway wrote:
On Mon, Aug 04, 2003 at 10:47:36AM +0200, Andreas Pflug wrote:
AFAICS the current implementation still doesn't have a way to access the
affected rowset, so it'a pretty much like a SELECT without a WHERE.
Yeah, unfortunately I didn't get a chance to implement this functi
On Fri, Aug 08, 2003 at 09:17:05AM +0800, Christopher Kings-Lynne wrote:
> australia=# \d affiliates_transactions
> View "public.affiliates_transactions"
[...]
> View definition:
> SELECT palm_buyers.affiliate_id, timestamptz(abstime(palm_buyers.datetime))
> AS
> date, 'Palm' AS "type", 1
On Fri, Aug 08, 2003 at 04:00:22PM -0400, Tom Lane wrote:
> Prepared statements would be just as much of a problem. I think the
> correct answer is simply "don't use those features in a pooled
> environment".
Well, unless you're prepared to manually manage these resources
yourself (i.e. DEALLOCAT
For the last few weeks (still haven't figure out what changed before
this started) one of our apps has been generating this error message on
the backend one or two times a day. I'm pretty sure it's not an
application error since it can be successfully re-run with the same
inputs. The application do
I grabbed REL7_4_BETA1 from cvs this morning, and am having a problem.
A trigger I wrote uses 'elog', which is apparently not defined any more
in my build. The documentation doesn't build (my problem), but
doc/src/sgml/spi.sgml indicates that elog should be valid.
The error I receive when insta
I ended up doing more or less what Bruce suggested, for 2 reasons -
first it is extensible, and second it avoids hardcoding any special
separators.
The new config variable is set like this:
log_line_format = '<%U%%%D> ' # %U=username %D=databasename %%=%
Sample output including session
On Fri, 8 Aug 2003 15:10:06 -0700, Sean Chittenden
<[EMAIL PROTECTED]> wrote:
>> Yes, we knew that already. Oliver had suggested simply dropping the
>> division by nKeys, thus pretending that the first-column correlation
>> is close enough. That seems to me to be going too far in the other
>> dir
On Sat, 9 Aug 2003 17:48:38 -0600
Robert Creager <[EMAIL PROTECTED]> said something like:
I received another hang, this time without a vacuum occurring. It occurred during a
copy operation. While there is a checkpoint process running, I don't believe it was
there at the start of the hang, but
--On Saturday, August 09, 2003 15:15:05 -0500 Larry Rosenman
<[EMAIL PROTECTED]> wrote:
--On Saturday, August 09, 2003 12:31:14 -0400 Tom Lane
<[EMAIL PROTECTED]> wrote:
Kurt Roeckx <[EMAIL PROTECTED]> writes:
If they don't have it defined, it's not going to do what we
expect and we might be
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > What would be interesting is a CREATE OR REPLACE functionality for
> > prepared cursors, where you could ask for it to be prepared, but if it
> > already existed, it would do nothing, or something like that.
>
> I don't think you coul
On Thu, 7 Aug 2003 13:44:19 -0700, Sean Chittenden
<[EMAIL PROTECTED]> wrote:
>> The indexCorrelation^2 algorithm was only a quick hack with no theory
>> behind it :-(. I've wanted to find some better method to put in there,
>> but have not had any time to research the problem.
>
>Could we "quick
Rod Taylor <[EMAIL PROTECTED]> writes:
> On Fri, 2003-08-08 at 16:00, Tom Lane wrote:
>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>>> Seems we have a problem with pooled connections and WITH HOLD cursors.
>>> We have code to reset transaction state and variables via RESET ALL, but
>>> how do we re
> >[...] it'd seem as though an avg depth of
> >nodes in index * tuples_fetched * (random_io_cost * indexCorrelation)
> >would be closer than where we are now...
>
> Index depth does not belong here because we walk down the index only
> once per index scan not once per tuple. It might be part of
The SCO compilers are notoriously buggy for the past 10-15 years.
---
Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > Larry just given me his own compiler and I still have the errors...
>
> [experiments a little...] Hmm.
Whew. To the best of my knowledge, JDBC at least doesn't provide any
API by which one could discover such a thing anyway, (although I guess a
given driver could implement some sort of statement cache with a name
lookup mechanism). I guess if it were part of the standards JDBC API
we'd have hea
I passed him mine, and he still sees it. Did either of you use -O without
-g?
I'll play tonite.
LER
--On Thursday, August 07, 2003 16:49:41 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
[EMAIL PROTECTED] writes:
UX:acomp: ERROR: "fe-protocol3.c", line 1402: internal compiler error:
can't deal wi
"Jenny -" <[EMAIL PROTECTED]> writes:
> hi, does anyone know what session level locks mean in postgresql..i've heard
> of table-level locks and row level locks but not session level
It's a hack for VACUUM. VACUUM needs to run two transactions to
vacuum both a table and its toast table; plus anot
On Wed, 06 Aug 2003 15:41:47 -0700
Joe Conway <[EMAIL PROTECTED]> said something like:
> Robert Creager wrote:
> > psql:dbTriggers.sql:30: ERROR: could not load library
> > "/usr/local/pgsql/triggers/tassiv_triggers.so":
> > /usr/local/pgsql/triggers/tassiv_triggers.so: undefined symbol: elog
> >
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> More to the point, this is highly incomplete... you did not teach the
>> adjacent getid routine about this, and there is code in (at least)
>> pg_dump.c that knows the quoting conventions used here.
> Hang on - those routines can parse the acl
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Ok, with using OUR src/port/getaddrinfo.c (by #undef'ing HAVE_GETADDRINFO
> and adding getaddrinfo.o to Makefile.global's LIBOBJS, it works again.
> We need to devise a configure test for broken/old getaddrinfo()'s.
That seems Turing-complete in gener
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> A variant (which'd be okay with me) is to separate these fields with
>> tabs instead of spaces; then the rule for DBAs would be "don't allow
>> tabs in db/user names".
> do you see: ^I that are "chars" th
I said:
> AFAICT, the diffs simply indicate that psql isn't echoing the input
> commands --- ie, it's not honoring the "\set ECHO all" command that
> is fed to it by the regression script. Which is odd in itself, and
> especially odd that it happens only in two out of 90-odd tests. I
> think you
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Seems we have a problem with pooled connections and WITH HOLD cursors.
We have code to reset transaction state and variables via RESET ALL, but
how do we remove WITH HOLD cursors when we pass a connection to a new
client?
Prepared s
We don't know the ramifications of doing that flag in the backend code,
and we don't know the performance problems of doing it in client
libraries.
First get your own platforms enabled for the existing thread flag, and
we can revisit this when most/all our platforms are supported. We want
to avo
Done.
---
Oleg Bartunov wrote:
> On Tue, 5 Aug 2003, Bruce Momjian wrote:
>
> > Oleg Bartunov wrote:
> > > Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
> >
> > Sorry, added:
> >
> >
Bruce Momjian wrote:
Tom Lane wrote:
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
It might be a bit risky getting pg_dump to use it though?
I definitely don't want pg_dump using the pretty-print stuff ;-).
I'm neutral on whether to use it in psql's \d commands.
I thought
38 matches
Mail list logo
