On Tue, 20 Feb 2007, FAST PostgreSQL wrote:
I think adding the 'format' of the log as an option in the 'destination'
may be confusing. We can have a new boolean variable like
'output_sql_log' or 'log_sql_format' which will trigger the output of
INSERT-able log in addition to syslog/stderr/eve
On Sun, 18 Feb 2007 18:25, Greg Smith wrote:
> On Sat, 17 Feb 2007, FAST PostgreSQL wrote:
> > #log_output_type = 'text' #Valid values are 'SQL' or 'text'
> > Defaults to 'text' which is status quo. If it is set to 'SQL' log will
> > be output as INSERT commands.
>
> This assumes someone wants eith
Jeremy Drake <[EMAIL PROTECTED]> writes:
> I will rename the functions regexp_split_to_(table|array) and I will add
> an optional limit parameter to the regexp_split_to_table function, for
> consistency and to avoid ordering concerns with LIMIT.
I'd go the other way: get rid of the limit option al
On Sun, 18 Feb 2007, Jeremy Drake wrote:
> On Sun, 18 Feb 2007, Peter Eisentraut wrote:
>
> > > regexp_split(string text, pattern text[, flags text]) returns setof
> > > text
> > >
> > > regexp_split_array(string text, pattern text[. flags text[, limit
> > > int]]) returns text[]
> >
> > Since you
On Sun, 18 Feb 2007, Peter Eisentraut wrote:
> Jeremy Drake wrote:
> > > As for the argument about array vs setof, I could see doing both to
> > > end the argument of which one is really superior for any particular
> > > problem.
> >
> > regexp_split(string text, pattern text[, flags text]) return
Please wait a little bit, I'll send updated patch (xpath_array() in core)
tonight or tomorrow.
It seems so that there is no actual needs in other xpath-functions...
Just to recall:
- xpath_array() produces xml[] as a result -- so, it's possible to process
then any of returned XML fragments, with
This is a TODO item:
o Allow psql \pset boolean variables to set to fixed values, rather
than toggle
Basically allows for:
test=# \pset expanded on
Expanded display is on.
test=# \pset footer off
Default footer is off.
test=# \pset footer
Default footer is on.
test=# \pset foote
Heikki Linnakangas wrote:
Alvaro Herrera wrote:
Here is a patch further cleaning up dummy process startup and the
bootstrap code itself a little.
Could we please call the "dummy" processes something else? Dummy
seems a bit belittling for such important things like bgwriter and the
startup proc
Jeremy Drake wrote:
> > As for the argument about array vs setof, I could see doing both to
> > end the argument of which one is really superior for any particular
> > problem.
>
> regexp_split(string text, pattern text[, flags text]) returns setof
> text
>
> regexp_split_array(string text, pattern
Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian wrote:
> > > Should we revisit xpath_array() for 8.3, or is this all in core
> > > now?
> >
> > Not yet, but we are currently discussing how.
>
> Uh, was this handled?
Not yet.
--
Peter Eisentraut
http://developer.postgresql.org/~p
Chad Wagner wrote:
> 1. if pset.notty is set and '-f' switch is not set then use
> simple_prompt -- deals with SQL script redirection case and '-f' is
> not used, and not interactive
> 2. else then use gets_fromFile(stdin)
> (read from stdin)
That seems a bit too complicated. Programs generally
Alvaro Herrera wrote:
Here is a patch further cleaning up dummy process startup and the
bootstrap code itself a little.
Could we please call the "dummy" processes something else? Dummy
seems a bit belittling for such important things like bgwriter and the
startup process.
How about worker or h
Added -hackers to CC:.
On 2/18/07, Greg Smith <[EMAIL PROTECTED]> wrote:
I've thought a bit about how to implement this TODO already (I have a log
file parser and I hate maintaining it)
Any problem using pgFouine?
Also, I feel that supporting the whole log_line_prefix syntax for this
feature
13 matches
Mail list logo
