Re: [HACKERS] patch for ja.po

Thank you, Kasahara-san. I think this is already patched in cvs of message catalogs. Could you try psql.po from http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgtranslation/messages/ja/psql.po regards, -- Shigehiro Honda From: Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp Subject:

Re: [HACKERS] Proposal: functions get_text() or get_url()

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 robertmh...@gmail.com On Wed, May 20, 2009 at 6:34 AM, Stefan Keller

Re: [HACKERS] [PATCH] cleanup hashindex for pg_migrator hashindex compat mode (for 8.4)

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

Re: [HACKERS] psql is broken in 8.4

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  That's odd. Work for

Re: [HACKERS] [PATCH] Compiler warning cleanup

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 );\ } !

Re: [HACKERS] information_schema.columns changes needed for OLEDB

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 are

Re: [HACKERS] information_schema.columns changes needed for OLEDB

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

[HACKERS] generic options for explain

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

Re: [HACKERS] information_schema.columns changes needed for OLEDB

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

[HACKERS] Allow vacuumdb to only analyze

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,

Re: [HACKERS] Allow vacuumdb to only analyze

On Sat, May 23, 2009 at 10:31 PM, decibel deci...@decibel.org 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

Re: [HACKERS] generic options for explain

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.