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.dump.gz
$
Good luck, Vadim !
Thanks for your work.
Oleg
On Sun, 10 Aug 2003, Vadim Mikheev wrote:
FarewellIt'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
Ah OK, I must have been thinking of the database owner check. I'd vote for
(1) checking that they own no objects and by default owning all their stuff
to the database owner. Plus add an optional clause:
DROP USER foo OWNER TO bob;
Chris
- Original Message -
From: Andrew Dunstan
-Original Message-
From: The Hermit Hacker [mailto:[EMAIL PROTECTED]
Sent: 11 August 2003 14:03
To: Vadim Mikheev
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] Farewell
I never know what to say in response to stuff like this ...
its like having to sign a card when a
Hello:
I want to know if postgresql 7.4 beta 1 can be configured under Cygwin
with SSL support ??
If the answer is positive how can i do it ?? or where can i found
documentation about this ( under linux or cygwin :) ) ??
Thanks in advance :)
--
Best regards
Carlos Guzmán Álvarez
On Monday 11 August 2003 00:36, Vadim Mikheev wrote:
FarewellIt'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.
D'Arcy J.M. Cain wrote:
On Monday 11 August 2003 00:36, Vadim Mikheev wrote:
FarewellIt'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
Bruce Momjian wrote:
How are statement level triggers supposed to work? Are they just
triggers deferred until the end of the statement? You mentioned access
to the affected rows, but I don't understand how that is supposed to
happen.
Statement level isn't about deferring or grouping the
Larry Rosenman [EMAIL PROTECTED] writes:
To fix it, remove -K inline from src/port/unixware's CFLAGS.
Dave Prosser of SCO has a fix, but this is the most expedient fix for now.
Do you think we should make that change for 7.4? Or will the workaround
be obsolete by the time 7.4 is released?
Bruce Momjian [EMAIL PROTECTED] writes:
TODO item?
Yeah. I'm leaning towards the idea that a protocol addition is what to
do.
Hm. Good thought. Maybe the same is true of held cursors.
It would be a simple addition at either the protocol or SQL level to
list the names of existing
AFAICS (part of) the real problem is in costsize.c:cost_index() where
IO_cost is calculated from min_IO_cost, pages_fetched,
random_page_cost, and indexCorrelation. The current implementation
uses indexCorrelation^2 to interpolate between min_IO_cost and
max_IO_cost, which IMHO gives
On Fri, Aug 08, 2003 at 15:32:05 +0530,
Rahul_Iyer [EMAIL PROTECTED] wrote:
hi,
im currently working on a project that requires batch operations - eg. Batch
insert/update etc. The database im using is PostgreSQL. However, i cannot
find any documentation for batch opeartions on PostgreSQL.
--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 better of using our replacement functions.
We will if we don't find struct addrinfo. See
On Fri, 08 Aug 2003 18:25:41 -0400, Tom Lane [EMAIL PROTECTED]
wrote:
Two examples: [...]
One more example:
X Y
A A
a B
A C
b A
B B
b C
C A
c B
C C
Bruce Momjian [EMAIL PROTECTED] writes:
Yes, I see those regularly too, and are related to bison issues.
The two 'defined but not used' warnings in pgc.c are a longstanding flex
(not bison) issue. (Hmm ... I wonder if they still happen in flex
2.5.31?) The other warning is not flex's fault ---
Bruce Momjian [EMAIL PROTECTED] writes:
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
Of course, now I've just gone to some trouble to accomodate funky
characters in user and dbnames in logging I'd have to kill him ...
:-)
Seriously, I think there's a good case for banning a few characters in
at least some names - like []'~#*|\ , say
andrew
Tom Lane wrote:
Andreas Pflug
Peter Eisentraut [EMAIL PROTECTED] writes:
Does anyone mind if I remove src/interfaces/cli? It's clearly outdated
and useless.
Looking at the CVS history, it seems that Lockhart had an idea of
building a CLI-spec-compatible interface on top of ecpg, but never
went further than an initial
Bruce, I know it's a bit picky but both below should be along the
lines of Allow thread-safe library since they are not threaded per
se.
L.
Bruce Momjian writes:
Libpq
Allow threaded with --enable-thread-safety (Lee Kindness, Bruce)
Miscellaneous Interfaces
Allow threaded ecpg with
--On Monday, August 11, 2003 20:36:11 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
On Mon, 11 Aug 2003, Bruce Momjian wrote:
Larry Rosenman wrote:
Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off
to prevent the setval() calls from halting
Of course, I was wrong. In fact, the patch below actually said it was
the pre-POSIX version of getpwuid_r().
---
Bruce Momjian wrote:
Actually, your getpwuid_r is the old, pre-POSIX format. The attached
email has the
- Original Message -
From: Gavin Sherry [EMAIL PROTECTED]
I am still researching ways of increasing performance of yacc parsers --
there is a very small amount of information on the Web concerning this --
I know some people who will tell you that the best way of improving
performance
Not sure I care for the vacuum part of that, but how about this
variant: DROP USER sets a flag in pg_shadow to disable login, and
the pg_shadow entry isn't removed, ever. (We could tweak the pg_user
view to hide dropped users, but anything looking directly at pg_shadow
would have to be
23 matches
Mail list logo
