Lamar Owen writes:
In the environment of the general purpose OS upgrade, the RPM's
installation scripts cannot fire up a backend, nor can it assume one
is running or is not running, nor can the RPM installation scripts
fathom from the run-time environment whether they are being run from a
Tom Lane writes:
1. If DECLARE CURSOR does not contain a LIMIT, continue to plan on the
basis of 10%-or-so fetch
I'd say that normally you're not using cursors because you intend to throw
away 80% or 90% of the result set, but instead you're using it because
it's convenient in your
Peter Mount writes:
Did that, and it still doesn't substitute @abs_top_srcdir@
Hmm, if you have "configure" revision 1.74 then you should certainly get
something for @abs_top_srcdir@. Try to remove config.cache and re-run
configure by hand. Most odd...
--
Peter Eisentraut [EMAIL
Adriaan Joubert writes:
2. We don't handle bit string and hex string literals correctly;
the scanner converts them into integers which seems quite at variance
with the spec's semantics.
This is still a problem that needs to be fixed.
I have gotten the B'1001'-style syntax to work, but
At 10:51 31/10/00 +0100, Peter Eisentraut wrote:
Tom Lane writes:
1. If DECLARE CURSOR does not contain a LIMIT, continue to plan on the
basis of 10%-or-so fetch
I'd say that normally you're not using cursors because you intend to throw
away 80% or 90% of the result set, but instead you're
Peter Eisentraut wrote:
Adriaan Joubert writes:
2. We don't handle bit string and hex string literals correctly;
the scanner converts them into integers which seems quite at variance
with the spec's semantics.
This is still a problem that needs to be fixed.
I have gotten the
At 14:14 31/10/00 +0100, Zeugswetter Andreas SB wrote:
Which is why I like the client being able to ask the
optimizer for certain kinds of solutions *explicitly*.
Yes, something like:
set optimization to [first_rows|all_rows]
That's one way that is usefull for affecting all
Hello,
there's really wierd trouble.
When I run 2 vacuum's in parallel they hangs. Both.
I use PostgreSQL from 7.0.x CVS (almost 7.0.3).
Any ideas? Tom?
--
Sincerely Yours,
Denis Perchine
--
E-Mail: [EMAIL PROTECTED]
HomePage: http://www.perchine.com/dyp/
I never saw much traffic regarding Karel's work on making stored
proceedures:
http://people.freebsd.org/~alfred/karel-pgsql.txt
What happened with this? It looked pretty interesting. :(
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a
I believe that its just resting on Vadim again to give us the go ahead
... which I believe its always been on his shoulders, no? :)
Vadim?
I think that at least 1 2 from WAL todo (checkpoints and port to
machines without TAS) is required before beta. As well as more testing...
Did anyone
The first test did not go very well. I did a fresh compile, initdb,
started the postmaster, ran 'make installcheck' (sequential regression
tests), and sent a kill -QUIT to the postmaster during the
numeric test.
Then I restarted the postmaster and got a load of lines like
REDO @
* Steve Wolfe [EMAIL PROTECTED] [001031 13:47] wrote:
(Incidentally, we've toyed around with developping a
query-caching
system that would sit betwen PostgreSQL and our DB libraries.
Sounds amazing, but requires some research, I guess. However, in
many
cases one would
* Peter Eisentraut [EMAIL PROTECTED] [001031 12:57] wrote:
I'd like to add an option or two to restrict the set of users that can
connect to the Unix domain socket of the postmaster, as an extra security
option.
I imagine something like this:
unix_socket_perm = 0660
unix_socket_group =
I'd like to add an option or two to restrict the set of users that can
connect to the Unix domain socket of the postmaster, as an extra security
option.
I imagine something like this:
unix_socket_perm = 0660
unix_socket_group = pgusers
Obviously, permissions that don't have 6's in there don't
14 matches
Mail list logo
