On Aug 5, 2006, at 10:48 PM, Christopher Browne wrote:
Quoth [EMAIL PROTECTED] (David Fetter):
On Fri, Aug 04, 2006 at 02:37:56PM -0700, Neil Conway wrote:
On Fri, 2006-08-04 at 12:40 -0700, David Fetter wrote:
While I am not going to reopen the can of worms labeled 'bug
tracker', I think
Why make it so complicated?
There could be a guc to indicate that the client is interested in
progress updates. For the execution phase, elog(INFO,...) could be
emitted for each major plan node. (The client would probably run the
explain plan beforehand or it would be embedded in the elog).
Sorry- perhaps I misunderstand the purpose of your group, but how can
you claim to be making decisions on software in the public interest
on a private, paid-member mailing list?
-M
On Jul 16, 2006, at 2:10 PM, Josh Berkus wrote:
Folks,
Hopefully by now a bunch of you have joined as
A great first step would be to add elog(INFO,...) in some standardized
format over the wire so that clients can tell what's going on. It could
be triggered by a GUC which is off by default.
-M
On Jul 15, 2006, at 9:10 PM, Greg Stark wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Maybe we
Dear Hackers,
I would like to thank all of you for organizing, hosting, and attending
the 10th Anniversary PostgreSQL Conference last weekend. I was
especially interested in future PostgreSQL directions and that was
definitely the conference's theme. It was great to meet the community's
big
Why are only select, insert, update, and delete supported for $X binds?
Why can't preparation be used as a global anti-injection facility?
Example using the backend protocol for binds:
PREPARE TRANSACTION $1;
bind $1 ['text']
--syntax error at $1
Why am I able to prepare statements with the
It's worth noting that on Darwin (on Apple hardware) gettimeofday is
never a syscall whereas on Linux (AFAIK), it always is.
On Jun 8, 2006, at 7:58 PM, Mark Kirkwood wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Wow, that is slow. Maybe a problem in the kernel? Perhaps
I have created a directed graph using graphviz that shows the message
flow/event stream. Perhaps this will be helpful to someone. Of course,
corrections are also welcome.
http://www.themactionfaction.com/pg/PGXProtocol.dot
http://www.themactionfaction.org/pg/PGXProtocol.svg
On Apr 23, 2006, at 6:43 PM, Alvaro Herrera wrote:
Agent M wrote:
I have created a directed graph using graphviz that shows the message
flow/event stream. Perhaps this will be helpful to someone. Of course,
corrections are also welcome.
Interesting. I'm not sure how to read the graph
The general idea would be to still use UDP backend-stats but get rid
of
the pipe part (emulated by standard tcp sockets on win32), so we'd
still
have the lose packets instead of blocking when falling behind.
Right.
Please correct me if I am wrong, but using UDP logging on the same
computer
Unfortunately, there is still one serious deficiency with the solution
below- it may not be the actual information postgresql is currently
using to determine who can log in and how- the file can be easily
changed behind the scenes and there is currently no way to know.
I (speaking as a DBA)
But there is still no way to verify that the information in the file is
what postgres saw last. DBAs make mistakes too. A simple way to view
the current access state would be much appreciated.
On Apr 1, 2006, at 1:01 PM, Andrew Dunstan wrote:
Er, how can the file be changed behind the
Why is the schema ignored entirely when using listen/notify? I couldn't
find any mention of this in the documentation.
Ideally, it should support schemas (and store any string it takes) but
it should at least throw an error when a schema is prepended. I guess
the workaround is to simply
On Feb 14, 2005, at 9:27 PM, Abhijit Menon-Sen wrote:
I know UTF8 is a type of unicode but do we need to rename anything
from Unicode to UTF8?
I don't know. I'll go through the documentation to see if I can find
anything that needs changing.
It's not the documentation that is wrong. Specifying
Would the version bump be a good time to fix the UNICODE encoding
misnomer in database creation and in the backend param status? I assume
it should be UTFx.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
15 matches
Mail list logo
