Hello
why we develop a new syntax?
we should have a secondary function explain_query(query_string,
option) that returns setof some. Next function should be
explain_query_xml. I thing so for typical use EXPLAIN statement is
enough. And for machine procession some new function should be
perfect.
r
On Sat, May 23, 2009 at 10:31 PM, decibel wrote:
> One of the talks at PGCon (update in place?) recommended running vacuumdb -z
> to analyze all tables to rebuild statistics. Problem with that is it also
> vacuums everything. ISTM it'd be useful to be able to just vacuum all
> databases in a clust
One of the talks at PGCon (update in place?) recommended running
vacuumdb -z to analyze all tables to rebuild statistics. Problem with
that is it also vacuums everything. ISTM it'd be useful to be able to
just vacuum all databases in a cluster, so I hacked it into vacuumdb.
Of course, using
On 5/23/09 7:37 PM, Konstantin Izmailov wrote:
Number 4 is actually numeric_precision (I typed incorrectly). My
recollection is that numeric_precision sometimes expressed in radix 2
and it caused issues for Windows apps.
I agree on other issues. I was curious if database can help OLEDB driver
(t
Well, here we are! Yet another thread about some piece of information
that's omitted from EXPLAIN and can't easily be added because there
are a zillion things we want to add to EXPLAIN and it's not OK to bury
the user[1]! I've long been of the opinion that the right way to fix
this problem is to
Number 4 is actually numeric_precision (I typed incorrectly). My
recollection is that numeric_precision sometimes expressed in radix 2 and it
caused issues for Windows apps.
I agree on other issues. I was curious if database can help OLEDB driver (to
make it simpler). Anyway it can emulate values
On Friday 22 May 2009 18:27:01 Konstantin Izmailov wrote:
> As we discussed at pgcon2009 there are some changes/fixes necessary in
> information_schema.columns to allow correct work of applications and
> services via OLEDB on Windows. Here are some:
>
> 1. data_type field contains types names that
On Saturday 23 May 2009 00:04:26 Zdenek Kotala wrote:
> Attached patch fixes following sun studio compiler warning:
>
> "tsquery_op.c", line 193: warning: syntax error: empty declaration
[snip]
> --- 190,201
> PG_RETURN_BOOL( CONDITION );\
> }
>
> ! CMP
Heikki Linnakangas píše v čt 21. 05. 2009 v 16:53 +0300:
> Zdenek Kotala wrote:
>
> > Another problem is with resultset. When I run for example following
> > command I got this output:
> >
> > postgres=# select oid from pg_am;
> > oid
> > --
> > 403
> > 405
> > 783
> > 2742
> >
I forgot to fix contrib. Updated patch attached.
Zdenek
Zdenek Kotala píše v pá 22. 05. 2009 v 16:23 -0400:
> Attached patch cleanups hash index headers to allow compile hasham for
> 8.3 version. It helps to improve pg_migrator with capability to migrate
> database with hash index
Ok.
But again: There is a library mentioned and documented in the famous
PostgreSQL book from Douglas & Douglas called pgcurl (
http://gborg.postgresql.org/project/pgcurl/ ). Where's this gone?
Yours, S.
2009/5/20 Robert Haas
> On Wed, May 20, 2009 at 6:34 AM, Stefan Keller wrote:
> > Questions
11 matches
Mail list logo
