Nabble - PostgreSQL - Announce

pgpool-II 2.3/pgpoolAdmin 2.3 released

2009-12-07T18:50:05Z

Pgpool Gobal Development Group is pleased to announce the availability
of pgpool-II 2.3 the latest stable version of pgpool-II 2.3 series and
its dedicated administration tool pgpoolAdmin 2.3.

About pgpool-II 2.3:
This version enhances replication, especially CURRENT_TIMESTAMP,
CURRENT_DATE, now() etc. now can be properly replicated. Also
perforance of replication when num_init_children == 1 is
enhanced. Pgpool-II now records the status of down nodes, and remember
when it restarts to ensure that keep the node status as before. Also
some logs are enhanced and more fine fail over controls are
added. Please note that pgpool-II 2.3 includes all of enhancements and
fixes of pgpool-II 2.2.1 to 2.2.6.

pgpool-II 2.3 can be downloaded from:
http://pgfoundry.org/frs/download.php/2493/pgpool-II-2.3.tar.gz

About pgpoolAdmin 2.3:
pgpoolAdmin is a dedicated administration tool written in PHP for
pgpool-II 2.3 or before.

pgpoolAdmin 2.3 can be downloaded from:
http://pgfoundry.org/frs/download.php/2494/pgpoolAdmin-2.3.tar.gz
--
Tatsuo Ishii
SRA OSS, Inc. Japan

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

New PostgreSQL Committers

2009-12-07T02:49:13Z

On behalf of the core team, I'm pleased to announce that the
PostgreSQL Project has expanded it's team of "committers", those
people who are able to make direct changes to the PostgreSQL source
code respository. As the project is extremely conservative about any
changes made to the source code to minimise the risk of introducing
any bugs, commit access is only given to contributors who have
consistently shown they work to a very high standard and have shown
commitment to the project.

The new committers are:

Robert Haas: Robert developed the commitfest.postgresql.org website
which is used to manage the process by which features are added to
PostgreSQL. He has twice acted as commitfest manager, and submitted
numerous patches such as join removal, auto-generation of headers &
bki files and the TRUNCATE privilege.

Simon Riggs: Simon is well know for working on large enterprise
features for PostgreSQL, including Point In Time Recovery and
partitioning. Simon is currently working on allowing PITR slave
servers to be used for read-only queries.

Greg Stark: Greg has worked on low-level features in PostgreSQL,
including asynchronous pre-fetching of data and packed variable length
data types. Greg was also responsible for the CREATE INDEX
CONCURRENTLY feature.

ITAGAKI Takahiro: ITAGAKI-san has worked on countless patches for
PostgreSQL, both fixing bugs and writing new features, recently
including WHEN clauses for triggers, a buffer usage feature for
EXPLAIN and a new implementation of VACUUM FULL.

Congratulations!

--
Dave Page
PostgreSQL Core Team

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - December 06 2009 ==

2009-12-06T18:19:05Z

== PostgreSQL Weekly News - December 06 2009 ==

The current commitfest is ending soon. Keep reviewing others' patches
so you can start fresh on your own :)

PostgreSQL now has an official release support policy. Details below.
http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy

New Survey: How do you contribute to PostgreSQL?
http://www.postgresql.org/community

Jeff Davis presents Operator Exclusion Constraints at SFPUG on
Tuesday, December 8 in San Francisco.
http://postgresql.meetup.com/1/calendar/11928447/

The next AustinPUG meeting is Wednesday, December 9th, 2009. Jim
Nasby will talk about table inheritance.
http://pugs.postgresql.org/node/1500

The New York Capital District PUG's first meeting will be January 7,
2010.
http://nycdpug.x10hosting.com/

PGDay-Cuba 2010 will be held 4-6 February 2010, in La Havana at the
University of Science Informatic. Attendees from Cuba, the Dominican
Republic and Venezuela are invited.

== PostgreSQL Product News ==

COBOL-IT Precompiler for PostgreSQL released.
http://www.cobol-it.com/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=31&cntnt01detailtemplate=simple&cntnt01returnid=58

GT portalBase 2.4, a framework for PostgreSQL, released.
http://www.gtportalbase.com/

PostgreSQL Maestro 9.12, a GUI for administration and development on
Windows, released.
http://www.sqlmaestro.com/products/postgresql/maestro/

MicroOLAP Database Designer 1.2.9 for PostgreSQL released.
http://microolap.com/products/database/postgresql-designer/

PgCon 2010 will be held May 20-21 2010 in Ottawa with tutorials before
on the 18th and 19th. The RfP is open!
http://www.pgcon.org/2010/papers.php

pgpool-II 2.2.6, a connection pooler and more, released.
http://pgfoundry.org/projects/pgpool/

PostgreDAC 2.5.4 beta, a Delphi/C++ builder for PostgreSQL, released.
http://microolap.com/products/connectivity/postgresdac/download/

Quick Application Suite and Quick Application Builder released.
http://www.datawarestudio.com/

== PostgreSQL Jobs for December ==

http://archives.postgresql.org/pgsql-jobs/2009-12/threads.php

== PostgreSQL Local ==

Stefan Keller will be teach a course called, "Introducion to
PostGIS/PostgreSQL" at the University of Applied Sciences Rapperswil
(HSR) on January 14, 2010 in Zurich, Switzerland.
http://www.gis.hsr.ch/wiki/Agenda

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter
and Josh Berkus.

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Reviews ==

- Josh Tolley reviewed the PL/Python array support patch and sent a
patch atop it to fix regression tests.

- Jeff Davis reviewed Joachim Wieland's Listen/Notify patch and
requested further rework from the author.

- Andrew (RhodiumToad) Gierth reviewed Hitoshi Harada's patch to
improve window frame control with ROWS BETWEEN. To complete the
review, he will need a decision on the API for aggregate functions.

- Hitoshi Harada marked Andrew (RhodiumToad) Gierth's patch, "ready
for committer."

- Simon Riggs did a preliminary review of ITAGAKI Takahiro's
partitioning syntax patch.

- ITAGAKI Takahiro reviewed Greg Smith's patch to enable resetting
statistics.
== Applied Patches ==

Bruce Momjian committed:

- In pgsql/doc/src/sgml/ecpg.sgml, properly indent SGML.

- There is no reference to THREAD_SUPPORT outside configure, and it is
never set, so remove it.

- In pgsql/doc/src/sgml/hstore.sgml, update hstore docs, mostly
word-smithing. David E. Wheeler

- Add ProcessUtility_hook() to handle all DDL to contrib/pg_stat_statements.
Itagaki Takahiro.

- Revert due to Tom's concerns: Add ProcessUtility_hook() to handle
all DDL to contrib/pg_stat_statements.

- Adjust 'psql -f -' to behave like a normal file and honor the -1
flag. Report from Robert Haas.

- Enable thread safety on all platforms. This will either be followed
up by a more extensive patch, or reverted, depending on the build
farm results.

- Apply full patch to enable thread-safety by default, e.g. doc
changes.

Peter Eisentraut committed:

- In pgsql/doc/src/sgml/xfunc.sgml, in SRF example, move oldcontext
variable definition into the FIRSTCALL branch, which is how most
actual code is actually structured. Also fix slight whitespace
misalignment.

- In pgsql/doc/src/sgml/information_schema.sgml, add a sentence of
documentation about the differences between the *_privileges and the
role_*_grants views.

- Speed up information schema privilege views. Instead of expensive
cross joins to resolve the ACL, add table-returning function
aclexplode() that expands the ACL into a useful form, and join
against that. Also, implement the role_*_grants views as a thin
layer over the respective *_privileges views instead of essentially
repeating the same code twice. Fixes bug #4596. By Joachim
Wieland, with cleanup by me.

Tom Lane committed:

- In pgsql/src/backend/tsearch/dict_thesaurus.c, avoid core dump on
empty thesaurus dictionary. Per report from Robert Gravsjo.

- Teach the regular expression functions to do case-insensitive
matching and locale-dependent character classification properly when
the database encoding is UTF8. The previous coding worked okay in
single-byte encodings, or in any case for ASCII characters, but
failed entirely on multibyte characters. The fix assumes that the
<wctype.h> functions use Unicode code points as the wchar
representation for Unicode, ie, wchar matches pg_wchar. This is
only a partial solution, since we're still stupid about non-ASCII
characters in multibyte encodings other than UTF8. The practical
effect of that is limited, however, since those cases are generally
Far Eastern glyphs for which concepts like case-folding don't apply
anyway. Certainly all or nearly all of the field reports of
problems have been about UTF8. A more general solution would
require switching to the platform's wchar representation for all
regex operations; which is possible but would have substantial
disadvantages. Let's try this and see if it's sufficient in
practice.

- Instead of sending application_name as a SET command after the
connection is made, include it in the startup-packet options. This
makes it work more like every other libpq connection option, in
particular it now has the same response to RESET ALL as the rest.
This also saves one network round trip for new applications using
application_name. The cost is that if the server is pre-8.5, it'll
reject the startup packet altogether, forcing us to retry the entire
connection cycle. But on balance we shouldn't be optimizing that
case in preference to the behavior with a new server, especially
when doing so creates visible behavioral oddities. Per discussion.

- Mark application_name as GUC_REPORT so that the value will be
reported back to the client by the server. This might seem pretty
pointless but apparently it will help pgbouncer, and perhaps other
connection poolers. Anyway it's practically free to do so for the
normal use-case where appname is only set in the startup packet ---
we're just adding a few more bytes to the initial ParameterStatus
response packet. Per comments from Marko Kreen.

- In pgsql/src/backend/postmaster/postmaster.c, ignore attempts to set
"application_name" in the connection startup packet. This avoids a
useless connection retry and complaint in the postmaster log when
receiving a connection from 8.5 or later libpq. Backpatch in all
supported branches, but of course *not* HEAD.

- In pgsql/doc/src/sgml/ref/rollback_to.sgml, clarify what's supposed
to happen when a cursor FETCH is rolled back by aborting a
subtransaction. Per discussion with Heikki.

- In pgsql/src/include/catalog/pg_proc.h, don't use a duplicate OID
for aclexplode().

Teodor Sigaev committed:

- in contrib/btree_gist, prevent intersection of ranges during page
split. Changes are only optimization, so don't backpatch.

Heikki Linnakangas committed:

- Fix bug in temporary file management with subtransactions. A cursor
opened in a subtransaction stays open even if the subtransaction is
aborted, so any temporary files related to it must stay alive as
well. With the patch, we use ResourceOwners to track open temporary
files and don't automatically close them at subtransaction end
(though in the normal case temporary files are registered with the
subtransaction resource owner and will therefore be closed). At end
of top transaction, we still check that there's no temporary files
marked as close-at-end-of-transaction open, but that's now just a
debugging cross-check as the resource owner cleanup should've closed
them already.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

ITAGAKI Takahiro sent in another revision of the YAML output patch for
EXPLAIN.

ITAGAKI Takahiro sent in another revision of the VACUUM FULL patch per
review from Jeff Davis. Jeff Davis sent three patches atop that one.

Andrew (RhodiumToad) Gierth sent in another revision of the patch to
add ORDER BY to aggregates.

KaiGai Kohei sent in another revision of the SE-PostgreSQL patch.

ITAGAKI Takahiro sent in a patch to modify the result type of
pg_read_file to bytea.

Bruce Momjian sent in two revisions of a patch to enable thread safety
in client libraries by default.

Zdenek Kotala sent in another revision of a patch to correct the
Docbook path in Solaris.

Tsutomu Yamada sent in two revisions of a patch to support Windows 64.

Caleb Welton sent in two revisions of a patch to fix int2vectorin.

Jeff Davis sent in another revision of the operator exclusion
constraints patch per review from Robert Haas.

Michael Paquier sent in two more revisions of the patch to add shell
calls to pgbench, per review from Greg Smith.

ITAGAKI Takahiro sent in another revision of the ProcessUtility_hook
patch per feedback from Tom Lane.

Bruce Momjian sent in a patch to install PL/pgsql by default.

Tim Bunce sent in a patch to refactor PL/Perl, and a patch atop that
to add some new GUCs with promising names including
plperl.on_perl_init, plperl.on_trusted_init, and
plperl.on_untrusted_init, along with some bug fixes and general code
correctness improvements.

KaiGai Kohei sent in another revision of the ACL patch for large
objects.

ITAGAKI Takahiro sent in another revision of the SQL syntax patch for
partitioning.

Zdenek Kotala sent in another revision of the patch to enable pg_ctl
to do an initdb.

Hitoshi Harada sent in another revision of the ROWS functionality for
windowing per review from Andrew (RhodiumToad) Gierth.

Jeff Davis sent in another revision of the VACUUM FULL removal patch.

Greg Smith sent in a patch to enable resetting statistics.

Simon Riggs sent in a patch to fix an issue with running out of lock
space in certain hot standby scenarios.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Quick Application Suite - Quick Application Builder Released

2009-12-04T10:10:45Z

DatawareStudio.com is proud to announce the immediate availability of

Quick Application Suite and Quick Application Builder.

Developed by DotSolutions s.r.l, QaS and QaB dramatically simplify the
process of
creating and maintaining a web-based complex application for every day usage.
Their's unique features make Quick Application family the fastest web
application
development tools on earth.

Tested with most widley used portals and database servers, both open
source and
commercial, they allow web developers to build a complete application,
comprehensive of
strong data entry controls and impressive reports in a bunch of minutes.

You can combine them with leading Data Warehousing technology like
Pentaho, SpagoBI or
JasperIntelligence to add exclusive data entry characteristic to your
dashboard.
Their tide integration with Pentaho Data Integration (previosly known
as Kettle) allows
power users to add complex back end control logic every time is needed.
Or you can use them alone, just a WebPortal like Liferay, Jahia, Jboss Portal,
ExoPlatform, Jetspeed, to create all the applications your society requires.

And all can be done without writing a single line of
html/java/jsp/php/asp code, thank's
to a flexible user interface and standard sql syntax.

You can download Quick Application Builder community Edition for
PostgreSql at this URL:
http://www.datawarestudio.com/post_dload.php

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PostgreSQL Release Support Policy

2009-12-04T08:36:00Z

After a great deal of discussion in the community, the project's core
team have written a policy outlining the support lifecycle for major
PostgreSQL releases, which can be found on the wiki with other project
policies at http://wiki.postgresql.org/wiki/Policies.

We hope this document will help our users plan their deployments more
effectively.

--------
The PostgreSQL project aims to fully support a major release for five years.

After a release falls out of full support, we may (at our committer's
discretion) continue to apply further critical fixes to the source
code, on a best-effort basis. No formal releases or binary packages
will be produced by the project, but the updated source code will be
available from our source code control system.

This policy will be followed on a best-effort basis. In extreme cases
it may not be possible to support a release for the planned lifetime;
for example if a serious bug is found that cannot be resolved in a
given major version without significant risk to the stability of the
code or loss of application compatibility. In such cases, early
retirement of a major version may be required.

End Of Life (EOL) dates:

Version EOL Date
PostgreSQL 7.4 July 2010 (extended)
PostgreSQL 8.0 July 2010 (extended)
PostgreSQL 8.1 November 2010
PostgreSQL 8.2 December 2011
PostgreSQL 8.3 February 2013
PostgreSQL 8.4 July 2014
--------

--
Dave Page
PostgreSQL Core Team

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

GT portalBase version 2.4 released

2009-12-04T07:00:25Z

Announcing the release of version 2.4 of GT portalBase.

It's been a while since our last major announcement but there's been lots going on on the development front. The blog

www.gtportalbase.com/blog

has seen frequent updates over the past six months.

To summarise recent development, the focus has largely been on visualisations to give admins/managers insight on how portalBase is being used as a database agile development environment. Visualisation techniques such as treemaps and sparklines have been employed to display where and how database data is being utilised in an organisation and allow drilldown to detailed statistics. Dashboards show various statistics at operational, tactical and strategic levels.

Now that admins can clearly see what information users are finding most useful so that development priorities can be adjusted, the next visualisation work will be on automated data reporting for users, particularly reporting exceptions based on variance and trends. If you have any examples of database visualisations of this type that have been useful to you, or any that would be, whether or not you use portalBase, please let us know via the new

www.gtportalbase.com/forum

or feel free to post any other comments.

Finally following requests, the documentation has been updated with full installation instructions for those needing a local install rather than a hosted service.

Regards
Oliver Kohll

oliver@... / +44(0)845 456 1810 / +44(0)7814 828608

www.gtportalbase.com/blog - for news and announcements

Stand presentation

2009-12-03T13:42:51Z

Hello all,

For upcoming events (like FOSDEM) we want to use a computer plus LCD
which should run a presentation. The content should include:

- PostgreSQL (bummer)
- Unique and Key Features
- Communities
- Additional software (as example pgAdminIII, phpPgAdmin)
- Other events
- Notes about the current event (talks, party, workshops)

Because every supporter should be able to easily modify and extend this
presentation, i suggest OpenOffice Presenter. It's installed on many
computers, the format is compatible and it's easy to use.

Does someone like to create a first version of this presentation?

Thanks & bye

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

signature.asc (196 bytes) Download Attachment

ANN: PostgreSQL Data Wizard 9.12 released

2009-12-03T06:13:38Z

Hi!

SQL Maestro Group announces the release of PostgreSQL Data Wizard 9.12, a
powerful Windows GUI solution for PostgreSQL data management.

PostgreSQL Data Wizard provides you with a number of easy-to-use wizards to
convert any ADO-compatible database to the PostgreSQL database, import data
into PostgreSQL tables, export data from tables, views and queries to most
popular file formats as well as generate data-driven ASP.NET pages for your
PostgreSQL database.

The new version is immediately available for download at
http://www.sqlmaestro.com/products/postgresql/datawizard/download/

New features
=================

1. Data Import: now you can import data from XML, Microsoft Office Excel
2007 and Microsoft Office Access 2007 file formats along with Microsoft
Office Excel 97-2003, Microsoft Office Access, CSV, DBF, and Text files
supported in the previous versions. Also starting with this version you can
import Text and CSV data files stored in different encodings.

2. Data Import: now it is possible to empty target tables as well as execute
custom SQL scripts before and after the import.

3. Data Import: an ability of using the COPY command has been implemented.
This feature can speed up the import process up to 10 times.

4. Data Import: the wizard has been completely redesigned to improve the
look and feel and increase the usability.

5. Data Export: support for Microsoft Office Excel 2007, Microsoft Office
Word 2007, OpenDocument Spreadsheed, and OpenDocument Text file formats has
been implemented. Also now it is possible to select the result file
encoding. This wizard also has been completely redesigned.

6. Datapump: the conversion rules for fields and indexes become more
intelligent, so starting with this version most of source databases from
well-known DBMS can be transferred even with default settings (or with a
small customization). Also the speed of data transfer has been significantly
increased.

7. Starting with this version it is possible to connect to a remote server
via SSH tunnel using a key-based authentication (in addition to the
password-based authentication supported in the previous versions). To
establish a remote connection in this way, you have to provide a private key
(either in ssh.com or OpenSSH formats) and (optionally) a passphrase. This
version also introduces support for both SSH-1 and SSH-2 protocols (whereas
all the previous versions supported only SSH-1).

8. An Italian localization is now included into the installation package.

In addition to this, several bugs have been fixed and some other minor
improvements and corrections have been made. Full press-release is available
at:
http://www.sqlmaestro.com/news/company/data_wizard_family_updated_to_version_9_12/

Background information:
-----------------------
SQL Maestro Group offers complete database admin, development and management
tools for MySQL, SQL Server, PostgreSQL, Oracle, DB2, SQLite, SQL Anywhere,
Firebird and MaxDB providing the highest performance, scalability and
reliability to meet the requirements of today's database applications.

Sincerely yours,
The SQL Maestro Group Team
http://www.sqlmaestro.com

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PostgreSQL@FOSDEM 2010 - Call for talks

2009-12-03T02:48:22Z

FOSDEM (http://www.fosdem.org/2010/) is a major Free and Open Source
event held annually in Brussels, Belgium, and attended by around 4000
people. As in recent years, the PostgreSQL project will have a devroom
where we will be presenting a number of talks. The event will be held
on the 6 - 7th February 2010.

We're looking for developers, users and contributors to submit talks
for inclusion on the program. Any topic related to PostgreSQL is
acceptable as long as it is non-commercial in nature. Suggested topics
might include:

- Migration of systems to PostgreSQL
- Application development
- Benchmarking and tuning
- Spatial applications
- Hacking the code
- Data warehousing
- New features
- Tips and tricks
- Replication
- Case studies

We will have a number of 45 minutes slots, and may split one or more
into 3 back-to-back 15 minute slots if we receive suitable proposals.

Please submit your proposals to:

fosdem@...

and include the following information:

- Your name
- The title of your talk (please be descriptive, as titles will be
listed with ~250 from other projects)
- A short abstract of one to two paragraphs
- A short biography introducing yourself
- Links to related websites/blogs etc.

The deadline for submissions is 22nd December 2009.

See you in Brussels!

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Free VPS Hosting w/ PostreSQL - Limited # Available

2009-12-02T11:22:58Z

Hello fellow open-source users and developers,

My name is Marc Fournier, and I'd like to highlight Hub.org's monthly VPS
giveaway. In case you've never heard of hub.org:

- Hub.org is small, customer-oriented host which I founded during the
mid-1990s, in order to host the PG project

- Hub is a proud supporter of open-source software development and offers
a large choice of web hosting applications

In case you're unfamiliar with what a Virtual Private Server might be:

- A VPS is like a *private server* (i.e. you get full root access), but
much cheaper and without the hardware hassles;

- It's much more secure than a shared hosting account: user files are in a
completely air-tight environment;

I like to think of hub.org as special in the way we view our business.

Specifically, most of our users are not interested in the technicalities
of their hosting accounts at all. On the contrary, they just need their
site to be up and running.

If you've similar expectations, be sure to visit http://hub.org to see
what we can offer you.

In case you're wondering if a VPS is right for you, consider our limited
offer:

We're distributing 10 free Starter VPS accounts, on the first of each
month, on a first come first served basis. It runs just like any other
Starter account, you just don't have to pay for the *First Year* of
service on it -- you're still responsible for any form of over-usage
however.

To get yours, browse http://hub.org at 0:00 AST (that's 23:00 EST) on the
1st of the month, sign up for an *Annual Starter Package* and enter
"FreeHosting" in the Coupon Field.

If you need any further information, you're more than welcome to get in
touch:

Marc Fournier / CEO
sales at hub.org
http://hub.org

PS: In the event you decide to spread the word, don't miss our
affiliate program: http://affiliates.hub.org/affiliates/signup.php

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy@... http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@...

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

ANN: Database Designer for PostgreSQL 1.2.9 released!

2009-12-02T01:39:48Z

Version 1.2.9 (December 1, 2009)

Extended SQL Editor with code completion and syntax validation added.
Support for privileges added as well as Grant Manager for ACL editing.
Diagram objects drawing improved.

You're welcome to download the latest release from our website at:
http://microolap.com/products/database/postgresql-designer/download/

Full changelog:

[!] Extended SQL Editor with code completion and syntax validation added
[!] Grant manager for objects added
[!] Support for database objects privileges introduced
[+] "Execute Script In Single Transaction (Alt + F9)" functionality
added to SQL Executor
[+] "Override grant priveleges" option added to Database Modification
[+] Owner option added for objects to Database Generation dialog
[+] Privileges option added for objects to Database Generation dialog
[+] Several options added to Display Preferences dialog
[+] Support for database's LC_COLLATE and LC_CTYPE options added
[+] Support for VARIADIC parameters added
[+] Support for window functions added
[+] Tablespaces, Sequences and Roles added to Object Tree View
[*] Additional type modifers check added to Modify Engine
[*] Check for object identification added
[*] In-place creation of new trigger procedures inside Table Editor improved
[*] Quick Hand Tool Key is now set to spacebar by default
[*] Reverse Engineering dialog improved
[*] Stored routine processing improved in Modify Engine
[*] Undo\Redo improved
[-] "Access violation occurs after editing composite types in Type
Manager" bug fixed
[-] "Cannot cancel Reverse Engineering using progress window" bug fixed
[-] "Cannot delete all users using Role Manager" bug fixed
[-] "Cannot open model through Windows Explorer (double click) if
designer already launched" bug fixed
[-] "Generate Database ignores objects order from Selection tab" bug fixed
[-] "List index out of bounds in Run Script" error fixed
[-] "List index out of bounds trying to edit trigger in Table Editor" bug fixed
[-] "Modify Engine alters fields of "character" and "bit" types if
width specifier ommited" bug fixed
[-] "Modify Engine alters function if array parameters used in
definition" bug fixed
[-] "Modify Engine alters tables tablespace to "pg_default" bug fixed
[-] "Sometimes impossible to uncheck PK flag for column in the Table
Editor" bug fixed

Please don't hesitate to ask any questions or report bugs with our
Support Ticketing system available at
http://www.microolap.com/support/

--
Best regards,
Vadim Kapochenia <support@...>
MicroOLAP Technologies Ltd.
http://microolap.com
--

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Re: == PostgreSQL Weekly News - November 29 2009 ==

2009-11-30T22:06:10Z

On Sun, Nov 29, 2009 at 07:58:13PM -0800, David Fetter wrote:

> Tim Bunch sent in two revisions of a patch refactoring PL/Perl[U]
> per discussion.

Oops. That's Tim Bunce. Thanks to all who spotted this :)

Cheers,
David.
--
David Fetter <david@...> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@...
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PGCon 2010

2009-11-30T18:10:29Z

Hello folks,

PGCon 2010 will be held 20-21 May 2010, in Ottawa at the University of
Ottawa. It will be preceded by two days of tutorials on 18-19 May 2010.

We are now accepting proposals for talks.

If you are doing something interesting with PostgreSQL, please submit
a proposal. You might be one of the backend hackers or work on a
PostgreSQL related project and want to share your know-how with
others. You might be developing an interesting system using PostgreSQL
as the foundation. Perhaps you migrated from another database to
PostgreSQL and would like to share details. These, and other stories
are welcome. Both users and developers are encouraged to share their
experiences.

Here are a some ideas to jump start your proposal process:

- novel, unique or complex ways in which PostgreSQL are used
- migration of production systems to PostgreSQL
- data warehousing with PostgreSQL
- tuning PostgreSQL for different work loads
- replicating data on top of PostgreSQL
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- tuning PostgreSQL for different work loads
- tuning and benchmarking
- case studies and howtos
- location-aware software with PostGIS
- emerging features
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- how to use PostgreSQL with your particular environment

Both users and developers are encouraged to share their experiences.

The schedule is:

19 Dec 2009 Proposal acceptance begins
19 Jan 2010 Proposal acceptance ends
19 Feb 2010 Confirmation of accepted proposals

See also <http://www.pgcon.org/2010/papers.php>

Instructions for submitting a proposal to PGCon 2010 are available
from: <http://www.pgcon.org/2010/submissions.php>

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - November 29 2009 ==

2009-11-29T19:58:13Z

== PostgreSQL Weekly News - November 29 2009 ==

PostgreSQL RPM packages for Fedora-12 released:
http://yum.pgsqlrpms.org/news-fedora12-packages-released.php

== PostgreSQL Product News ==

apgdiff 1.4, a tool for comparing PostgreSQL schemas, released.
http://sourceforge.net/projects/apgdiff/

Karoo, a web GUI based on PostgreSQL, released.
http://www.zwartberg.com/cave.html

MyJSQLView 3.05, a Java-based GUI for PostgreSQL, released.

== PostgreSQL Jobs for November ==

http://archives.postgresql.org/pgsql-jobs/2009-11/threads.php

== PostgreSQL Local ==

The third edition of the Italian PostgreSQL Day will be held at the
University of Pisa on the 4th of December. Entrance is free.
Sponsors are welcome.
http://www.pgday.it/

Stefan Keller will be teach a course called, "Introducion to
PostGIS/PostgreSQL" at the University of Applied Sciences Rapperswil
(HSR) on January 14, 2010 in Zurich, Switzerland.
http://www.gis.hsr.ch/wiki/Agenda

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter
and Devrim GUNDUZ.

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Heikki Linnakangas committed:

- Fix an old bug in multixact and two-phase commit. Prepared
transactions can be part of multixacts, so allocate a slot for each
prepared transaction in the "oldest member" array in multixact.c. On
PREPARE TRANSACTION, transfer the oldest member value from the
current backends slot to the prepared xact slot. Also save and
recover the value from the 2PC state file. The symptom of the bug
was that after a transaction prepared, a shared lock still held by
the prepared transaction was sometimes ignored by other
transactions. Fix back to 8.1, where both 2PC and multixact were
introduced.

Magnus Hagander committed:

- In pgsql/src/interfaces/libpq/win32.mak, add missing library to
standalone libpq build on Win32. Hiroshi Saito.

Tom Lane committed:

- Use diff's -w switch only on Windows, to avoid problems with
inconsistent newline representations. Per buildfarm results and
subsequent discussion. Sync up a couple of other places that had
their own policies.

- Simplify psql's new linestyle behavior to default to linestyle=ascii
all the time, rather than hoping we can tell whether the terminal
supports UTF8 characters. Per discussion.

- In pgsql/doc/src/sgml/release-8.5.sgml, fix missing end tag, per
Jeff Davis.

- Eliminate a lot of list-management overhead within
join_search_one_level by adding a requirement that build_join_rel
add new join RelOptInfos to the appropriate list immediately at
creation. Per report from Robert Haas, the list_concat_unique_ptr()
calls that this change eliminates were taking the lion's share of
the runtime in larger join problems. This doesn't do anything to
fix the fundamental combinatorial explosion in large join problems,
but it should push out the threshold of pain a bit further. Note:
because this changes the order in which joinrel lists are built, it
might result in changes in selected plans in cases where different
alternatives have exactly the same costs. There is one example in
the regression tests.

- Add support for an application_name parameter, which is displayed in
pg_stat_activity and recorded in log entries. Dave Page, reviewed
by Andres Freund.

- Add support for anonymous code blocks (DO blocks) to PL/Perl. Patch
by Joshua Tolley, reviews by Brendan Jurd and Tim Bunce.

- Make pg_stat_activity.application_name visible to all users, rather
than being hidden when current_query is. Relocate it to a column
position more consistent with that behavior. Per discussion.

- Add some opr_sanity checks that the lengths of the various
argument-info arrays in a pg_proc entry match. Seems like an easy
mistake to make when manually adjusting these values in a pg_proc.h
entry.

- In pgsql/src/pl/plperl/plperl.c, fix session-lifespan memory leak
when a plperl function is redefined: we have to tell Perl it can
release its compiled copy of the function text. Noted by Alexey
Klyukin. Back-patch to 8.2 --- the problem exists further back, but
this patch won't work without modification, and it's probably not
worth the trouble.

Peter Eisentraut committed:

- Add PG_MODULE_MAGIC and some missing include files to examples.
Euler Taveira de Oliveira.

- In pgsql/doc/src/sgml/func.sgml, fix syntax in extract() examples.
Erik Rijkers.

- In pgsql/src/interfaces/libpq/fe-connect.c, remove prefix "ERROR:"
from some messages, to make everything consistent

- In pgsql/src/interfaces/libpq/fe-connect.c, error when a specified
connection service is not found, instead of ignoring it.

Michael Meskes committed:

- In pgsql/src/interfaces/ecpg/ecpglib/misc.c, made function better
readable.

- Added dynamic cursor names to ecpg. Almost the whole patch was done
by Boszormenyi Zoltan, with only a minor tweak or two from me.

- In pgsql/src/interfaces/ecpg/preproc/ecpg.addons, synced addon rules
after some renamings.

- In pgsql/src/interfaces/ecpg/ChangeLog, forgot to add dynamic
cursors to Changelog.

- In ECPG, added missing files.

- In ECPG, added script to check if all rule re-definition in
ecpg.addons are indeed used in the build process. If not the build
process will stop with an error message.

- In pgsql/src/interfaces/ecpg/ecpglib/data.c, if no result is given
NOTFOUND should be returned. Check for empty result string too.

- In pgsql/src/interfaces/ecpg/preproc/ecpg.addons, remove */
characters from declare cursor statements before putting them into a
comment.

Bruce Momjian committed:

- In pgsql/doc/src/sgml/ref/vacuumdb.sgml, document ath vacuumdb
--analyze does analyze _also_, not in place of vacuum.

- Improve test descriptions displayed during test_fsync; increase
default loops to 5k.

- Add link to external fsync testing script and our fsync test tool.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Marko (johto) Tiikkaja sent in another revision of the writeable CTE
patch. Tom Lane responded with another one.

Teodor Sigaev sent in a patch to add red-black trees to GIN.

Teodor Sigaev sent in a patch to add some point operations for GiST.

Teodor Sigaev sent in a patch to add a supplied module which does
K-nearest-neighbor efficiently using GiST.

Alexey Klyukin sent in a patch to improve PL/Perl's support for
PostgreSQL arrays.

Daniel Farina sent in a group of patches to allow COPY TO FUNCTION and
add support to same to dblink.

Andrew Dunstan sent in a patch to allow ragged COPYing.

Per a review by Jeff Janes, ITAGAKI Takahiro sent in another revision
of the patch to add a BUFFERS option to EXPLAIN.

Tim Bunch sent in two revisions of a patch refactoring PL/Perl[U] per
discussion.

Zdenek Kotala sent in a patch to refactor the path Docbook uses so it
works better on Solaris.

Jeff Davis sent on three more revisions of the operator exclusion
constraints patch.

ITAGAKI Takahiro sent in another revision of the partitioning syntax
patch.

Magnus Hagander sent in a patch to add git to the PostgreSQL official
documentation.

Teodor Sigaev sent in two revisions of a WIP patch to add
k-nearest-neighbor searches to GiST.

Robert Haas sent in another revision of the patch to allow people to
set random_page_cost and seq_page_cost per tablespace.

Simon Riggs sent in a patch to fix some issues in hot standby.

Jeff Davis sent in a doc patch atop the new VACUUM FULL patch.

Hitoshi Harada sent in another revision of the patch to add more ROWS
options for frames in windowing functions.

Magnus Hagander sent in a patch to fix LDAP.

Kurt Harriman sent in a patch to remove a gcc dependency in the
definition of inline functions.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PostgreSQL RPM packages for Fedora-12 released

2009-11-25T11:25:33Z

Thanks everyone who pestered me last week after Fedora-12 was
announced. :) PostgreSQL RPM packages for Fedora-12 was released:

http://yum.pgsqlrpms.org/8.4/fedora/fedora-12-i386/repoview/
http://yum.pgsqlrpms.org/8.4/fedora/fedora-12-x86_64/repoview/
http://yum.pgsqlrpms.org/8.3/fedora/fedora-12-i386/repoview/

These sets include almost all of the packages that are supported by RPM
Building Project. More will come soon.

For details, please visit here:

http://yum.pgsqlrpms.org/howtoyum.php

Regards,
--
Devrim GÜNDÜZ , RHCE
Professional Services, Training, 24x7 Support
Authors: PostgreSQL Replicator, ODBCng, PostgreSQL RPMs, PITRTools
http://www.commandprompt.com/ XMPP: dgunduz@...
Twitter: http://twitter.com/devrimgunduz

signature.asc (204 bytes) Download Attachment

Incredibly simple PostgreSQL to WEB GUI system

2009-11-23T05:19:27Z

Create an entire web application by just writing SQL, HTML, and some
XML configuration. No other coding, no PHP or C++, etc. is required...
though you can add that too, if you like. See:

http:/www.zwartberg.com/cave.html

Following is a very simplistic example of a "cave" service:

<database name="KarooDB" username="bmodra" password=""
connect_timeout="1" connection-pool-size="3"/>
<service name="list-stock" id="list-stock">
<sql>
select owner,type,value,count,id from
stock where owner=<parameter name="owner" type="quoted-string"/>;
</sql>
</service>

Following is the corresponding html:

<table>
<tbody>
<tr>
<th>owner</th>
<th>type</th>
<th>value</th>
<th>count</th>
<th>id</th>
</tr>
<tr id="test">

<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

You can probably figure out the rest: the rows returned replace the
html comments, and the <tr> (template) gets repeated for each row.
This is a very simplistic example... see the following URL for a more
compete example:
http://www.zwartberg.com/surf.html

--
Brian Modra Land line: +27 23 5411 462
Mobile: +27 79 69 77 082
5 Jan Louw Str, Prince Albert, 6930
Postal: P.O. Box 2, Prince Albert 6930
South Africa
http://www.zwartberg.com/

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - November 22 2009 ==

2009-11-22T18:56:38Z

== PostgreSQL Weekly News - November 22 2009 ==

A report from the Brazilian PostgreSQL conference in Portuguese is at:
http://pgcon.postgresql.org.br/2009/asl/pgcconbr-2009_prest_contas.pdf

== PostgreSQL Product News ==

pgstat 1.1 released.
http://pgfoundry.org/projects/pgstat2/

== PostgreSQL Jobs for November ==

http://archives.postgresql.org/pgsql-jobs/2009-11/threads.php

== PostgreSQL Local ==

The third edition of the Italian PostgreSQL Day will be held at the
University of Pisa on the 4th of December. Entrance is free.
Sponsors are welcome.
http://www.pgday.it/

Stefan Keller will be teach a course called, "Introducion to
PostGIS/PostgreSQL" at the University of Applied Sciences Rapperswil
(HSR) on January 14, 2010 in Zurich, Switzerland.
http://www.gis.hsr.ch/wiki/Agenda

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Tom Lane committed:

- In pgsql/src/backend/optimizer/plan/setrefs.c, while doing the final
setrefs.c pass over a plan tree, try to match up non-Var sort/group
expressions using ressortgroupref labels instead of depending
entirely on equal()-ity of the upper node's tlist expressions to the
lower node's. This avoids emitting the wrong outputs in cases where
there are textually identical volatile sort/group expressions, as
for example:
SELECT DISTINCT random(), random() FROM generate_series(1,10);
Per report from Andrew Gierth. Backpatch to 8.4. Arguably this is
wrong all the way back, but the only known case where there's an
observable problem is when using hash aggregation to implement
DISTINCT, which is new as of 8.4. So for the moment I'll refrain
from backpatching further.

- Provide a parenthesized-options syntax for VACUUM, analogous to that
recently adopted for EXPLAIN. This will allow additional options to
be implemented in future without having to make them fully-reserved
keywords. The old syntax remains available for existing options,
however. Itagaki Takahiro

- Add a hook to CREATE/ALTER ROLE to allow an external module to check
the strength of database passwords, and create a sample
implementation of such a hook as a new contrib module
"passwordcheck". Laurenz Albe, reviewed by Takahiro Itagaki.

- In pgsql/src/backend/postmaster/syslogger.c, fix memory leak in
syslogger: logfile_rotate() would leak a copy of the output filename
if CSV logging was enabled and only one of the two possible output
files got rotated during a particular call (which would, in fact,
typically be the case during a size-based rotation). This would
amount to about MAXPGPATH (1KB) per rotation, and it's been there
since the CSV code was put in, so it's surprising that nobody
noticed it before. Per bug #5196 from Thomas Poindessous.

- Add a WHEN clause to CREATE TRIGGER, allowing a boolean expression
to be checked to determine whether the trigger should be fired. For
BEFORE triggers this is mostly a matter of spec compliance; but for
AFTER triggers it can provide a noticeable performance improvement,
since queuing of a deferred trigger event and re-fetching of the
row(s) at end of statement can be short-circuited if the trigger
does not need to be fired. Takahiro Itagaki, reviewed by KaiGai
Kohei.

- Fix display and dumping of UPDATE OR TRUNCATE triggers (a bizarre
combination maybe, but we should get it right). Bug noted while
reviewing TRIGGER WHEN patch. Already fixed in HEAD.

- Refactor ecpg grammar so that it uses the core grammar's
unreserved_keyword list, minus a few specific words that have to be
treated specially. This replaces a hard-wired list of keywords that
would have needed manual maintenance, and was not getting it. The
8.4 coding was already missing these words, causing ecpg to
incorrectly treat them as reserved words: CALLED, CATALOG, DEFINER,
ENUM, FOLLOWING, INVOKER, OPTIONS, PARTITION, PRECEDING, RANGE,
SECURITY, SERVER, UNBOUNDED, WRAPPER. In HEAD we were additionally
missing COMMENTS, FUNCTIONS, SEQUENCES, TABLES. Per gripe from
Bosco Rama.

- Improve psql's tabular display of wrapped-around data by inserting
markers in the formerly-always-blank columns just to left and right
of the data. Different marking is used for a line break caused by a
newline in the data than for a straight wraparound. A newline break
is signaled by a "+" in the right margin column in ASCII mode, or a
carriage return arrow in UNICODE mode. Wraparound is signaled by a
dot in the right margin as well as the following left margin in
ASCII mode, or an ellipsis symbol in the same places in UNICODE
mode. "\pset linestyle old-ascii" is added to make the previous
behavior available if anyone really wants it. In passing, this
commit also cleans up a few regression test files that had
unintended spacing differences from the current actual output.
Roger Leigh, reviewed by Gabrielle Roth and other members of PDXPUG.

- In pgsql/src/test/regress/expected/xmlmap.out, ooops, forgot to
check the libxml cases for psql output wrapping change.

- In pgsql/src/test/regress/pg_regress.c, remove -w
(--ignore-all-space) option from pg_regress's diff calls. We have
used -w for a long time as a means of reducing the reported diff
volume when one element of a result table isn't of the expected
width. However, most of the time the results just pass anyway, so
this isn't as important as it once was. Meanwhile, the risk of
missing potentially significant deviations has gone up, particularly
with psql's ability to report error cursor positions. So, let's
switch over to space-sensitive comparisons. Per my proposal of
yesterday. (All the expected files that I can test here seem to be
ready for this already, but we'll see what the buildfarm thinks
about others.)

- In pgsql/src/test/regress/output/largeobject_1.source, adjust
expected-results spacing per buildfarm results.

- In pgsql/doc/src/sgml/ref/psql-ref.sgml, assorted wordsmithing on
the documentation of \pset --- try to make it a bit more consistent
and less obviously written by different people at different times.

Peter Eisentraut committed:

- In pgsql/src/bin/pg_dump/pg_restore.c, typo: dump -> restore. Fixed
in 8.4 and 8.5 Author: Guillaume Lelarge <guillaume@...>

- In pgsql/src/bin/psql/mainloop.c, ignore UTF-8-encoded Unicode
byte-order mark at the beginning of a file if the client encoding is
UTF-8. A limited version of a patch proposed by Itagaki Takahiro

Magnus Hagander committed:

- Revert backpatch of inheritable-ACE patch for Win32, since it broke
compatibility with pre-Windows 2000 versions.

Heikki Linnakangas committed:

- In pgsql/src/backend/optimizer/path/allpaths.c, remove superfluous
curly brace, fixing compilation with OPTIMIZER_DEBUG. Jan Urbanski.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

ITAGAKI Takahiro sent in another revision of the VACUUM FULL
refactoring patch.

Josh Tolley sent in three more revisions of the patch to enable
PL/Perl[U] anonymous DO blocks. Tim Bunce sent in a patch atop same
loosening some restrictions.

Zoltan Boszormenyi sent in new revisions of the patches for ECPG
implementing dynamic cursor names, SQLDA support, DESCRIBE [OUTPUT]
and out-of-scope cursor support in Informix mode.

Alvaro Herrera sent in a patch to add copydatum to SPI.

Pavel Stehule sent in another revision of the patch to allow SQL to
use psql parameters.

Heikki Linnakangas sent in a patch intended to fix a bug in the
interaction between multixacts and prepared transactions.

Alex Hunsaker sent in a patch atop Marko (johto) Tiikkaja's writeable
CTE patch along with a review.

Pavel Stehule sent in a patch to add a USING clause to OPEN FOR
EXECUTE in PL/pgsql.

Robert Haas sent in a patch atop Jeff Davis's patch to replace the
existing strategy numbers with operator OIDs.

Hannu Valtonen sent in a patch to add in-line (DO) support to
PL/PythonU.

Euler Taveira de Oliveira sent in a doc patch which adds a
PG_MODULE_MAGIC block to C examples.

George Gensure sent in a patch to reference function parameters by
name.

Joachim Wieland sent in two more revisions of the patch to add
payloads to NOTIFY.

James Pye sent in a patch to add the PL/Python3 language.

Emmanuel Cecchet sent in three more revisions of the partitioning
grammar patch.

David Wheeler sent in a doc patch for hstore.

Hiroshi Saito sent in a patch to fix win32.mak.

Andrew Dunstan sent in a WIP patch to log queries automatically in
auto-explain.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

MyJSQLView Version 3.05 Released

2009-11-21T10:36:08Z

The MyJSQLView project is pleased to provide the incremental release of
Version 3.05 to the public. The release will be short lived because a
follow on version with an initial plugin feature will come out by the
end of the month. The release v3.05 fixes some minor bugs in the program
such as SQL exports having semicolons being stripped out, and Summary
Table state loading/restore of the sort order. Several new features have
been added to the program, Delete All Table Rows, Summary Table CSV
Pasting from a spreadsheet, and an Update Multiple Table Rows mechanism.
Generally the project is still on track to have a plugin architecture
implemented for future enhancements.

Dana M. Proctor
MyJSQLView Project Manager
http://dandymadeproductions.com/projects/MyJSQLView/index.html

MyJSQLView provides an easy to use Java based interface for viewing,
adding, editing, or deleting entries in a PostgreSQL databases. A query
frame allows the building of complex SELECT SQL statements. The
application allows easy sorting, searching, and import/export of table
data.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Nov/Dec 2009 Open Source Database Magazine Released!

2009-11-18T19:45:13Z

Exciting news!

The next issue of Open Source Database Magazine (http://www.osdbzine.net)
is now available. This information-packed issue has over 60 pages of
information including:

* Firebirds Road Trip and Whats New with 2.5
* Coding Corner: Trees Wheres the Performance?
* PostgreSQLs tsvector: Secret Sauce for Search Engines
* The Lab: The XtraBackup Program for MySQL Part Two
* Drizzle A Lightweight Database for the Web
* Kontrollbase: Enterprise grade MySQL monitoring and analytics
* Creating a Twitter Mashup with MongoDB
* Introducing LucidDB

Plus the usual news and views. All of this for $4.95. It is simply the
biggest and the best issue we have ever released. Ready to sign up? Head
over to http://www.osdbzine.net/signup.html to register and then you can
download the new issue. Curious as to what this is all about? I just
posted an online addendum to the Drizzle article in our free content
section (http://www.osdbzine.net/free.html) that will give you a taste of
what you can expect.

Thanks to the contributors. You all did a great job and I appreciate it!

Sorry the website isnt currently as polished as the magazine. While it
doesnt look pretty, it is functioning. And now that the magazine is out I
can turn my attention to it again. If you experience any problems let me
know at editor AT osdbzine.net.

thanks,

keith

--
Editor
Open Source Database Magazine
http://www.osdbzine.net
editor@...

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - November 15 2009 ==

2009-11-15T23:56:06Z

== PostgreSQL Weekly News - November 15 2009 ==

Commitfest for November, 2009 has begun. Start reviewing other
people's patches!

New Survey: Which 8.5 Alpha 2 feature have you tried?
http://www.postgresql.org/community/

== PostgreSQL Jobs for November ==

http://archives.postgresql.org/pgsql-jobs/2009-11/threads.php

== PostgreSQL Local ==

OpenSQL Camp will be November 14-15, 2009 in Portland, OR
http://www.chesnok.com/daily/2009/07/29/opensql-camp-comes-to-portland-november-14-15-2009/

JPUG 10th Anniversary Conference is November 20-21, 2009 in Tokyo, Japan.
http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php

Stefan Keller will be teach a course called, "Introducion to
PostGIS/PostgreSQL" at the University of Applied Sciences Rapperswil
(HSR) on January 14, 2010 in Zurich, Switzerland.
http://www.gis.hsr.ch/wiki/Agenda

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter
and Josh Berkus.

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Tom Lane committed:

- Re-refactor the core scanner's API, in order to get out from under
the problem of different parsers having different YYSTYPE unions
that they want to use with it. I defined a new union core_YYSTYPE
that is just the (very short) list of semantic values returned by
the core scanner. I had originally worried that this would require
an extra interface layer, but actually we can have parser.c's
base_yylex (formerly filtered_base_yylex) take care of that at no
extra cost. Names associated with the core scanner are now
"core_yy_foo", with "base_yy_foo" being used in the core Bison
parser and the parser.c interface layer. This solves the last
serious stumbling block to eliminating plpgsql's separate lexer.
One restriction that will still be present is that plpgsql and the>
core will have to agree on the token numbers assigned to tokens that
can be returned by the core lexer. Since Bison doesn't seem willing
to accept external assignments of those numbers, we'll have to live
with decreeing that core and plpgsql grammars declare these tokens
first and in the same order.

- More incremental refactoring in plpgsql: get rid of gram.y
dependencies on yytext. This is a necessary change if we're going
to have a lexer interface layer that does lookahead, since yytext
won't necessarily be in step with what the grammar thinks is the
current token. yylval and yylloc should be the only side-variables
that we need to manage when doing lookahead.

- In pgsql/src/backend/commands/tablespace.c, revert the temporary
patch to work around Snow Leopard readdir() bug. Apple has fixed
that bug in 10.6.2, and we should encourage users to update to that
version rather than trusting this cosmetic patch. As was recently
noted by Stephen Tyler, this patch was only masking the problem in
the context of DROP TABLESPACE, but the failure could occur in other
places such as pg_xlog cleanup.

- Do not build psql's flex module on its own, but instead include it
in mainloop.c. This ensures that postgres_fe.h is read before
including any system headers, which is necessary to avoid problems
on some platforms where we make nondefault selections of feature
macros for stdio.h or other headers. We have had this policy for
flex modules in the backend for many years, but for some reason it
was not applied to psql. Per trouble report from Alexandra Roy and
diagnosis by Albe Laurenz.

- Remove plpgsql's separate lexer (finally!), in favor of using the
core lexer directly. This was a lot of trouble, but should be worth
it in terms of not having to keep the plpgsql lexer in step with
core anymore. In addition the handling of keywords is significantly
better-structured, allowing us to de-reserve a number of words that
plpgsql formerly treated as reserved.

- Remove pg_parse_string_token() --- not needed anymore.

- Make initdb behave sanely when the selected locale has codeset
"US-ASCII". Per discussion, this should result in defaulting to
SQL_ASCII encoding. The original coding could not support that
because it conflated selection of SQL_ASCII encoding with not being
able to determine the encoding. Adjust pg_get_encoding_from_locale()'s
API to distinguish these cases, and fix callers appropriately. Only
initdb actually changes behavior, since the other callers were
perfectly content to consider these cases equivalent. Per bug #5178
from Boh Yap. Not going to bother back-patching, since no one has
complained before and there's an easy workaround (namely, specify
the encoding you want).

- In pgsql/src/port/chklocale.c, check for C/POSIX before assuming
that nl_langinfo or win32_langinfo will work. Per buildfarm
results.

- In pgsql/src/backend/utils/misc/guc-file.l, the recent patch to log
changes in postgresql.conf settings dumped core if the initial value
of a string variable was NULL, which is entirely possible. Noted
while experimenting with custom_variable_classes.

- Add control knobs for plpgsql's variable resolution behavior, and
make the default be "throw error on conflict", as per discussions.
The GUC variable is plpgsql.variable_conflict, with values "error",
"use_variable", "use_column". The behavior can also be specified
per-function by inserting one of #variable_conflict error,
#variable_conflict use_variable, #variable_conflict use_column at
the start of the function body. The 8.5 release notes will need to
mention using "use_variable" to retain backward-compatible behavior,
although we should encourage people to migrate to the much less
mistake-prone "error" setting. Update the plpgsql documentation to
match this and other recent changes.

- In pgsql/src/include/nodes/parsenodes.h, avoid assuming that enum
CreateStmtLikeOption is unsigned. Zdenek Kotala

- In pgsql/src/backend/parser/parse_utilcmd.c, clean up a couple of
bizarre code formatting choices in recent CREATE LIKE patch.

- Make unaccent's install/uninstall scripts look more like all the
others. Set search_path explicitly, don't use IF EXISTS, etc.

- Improve planning of Materialize nodes inserted atop the inner input
of a mergejoin to shield it from doing mark/restore and refetches.
Put an explicit flag in MergePath so we can centralize the logic
that knows about this, and add costing logic that considers using
Materialize even when it's not forced by the previously-existing
considerations. This is in response to a discussion back in August
that suggested that materializing an inner indexscan can be helpful
when the refetch percentage is high enough.

Bruce Momjian committed:

- In pgsql/doc/src/sgml/plpgsql.sgml: PL/pgSQL FOUND, document that
GET DIAGNOSTICS is affected by EXECUTE, while FOUND is not.

- In pgsql/doc/src/sgml/plpgsql.sgml: PL/pgSQL FOUND, update wording
of GET DIAGNOSTICS/FOUND, per David Fetter.

- In pgsql/src/backend/utils/adt/timestamp.c, add C comment about why
there is no interval_abs(): it is unclear what value to return.
http://archives.postgresql.org/pgsql-general/2009-10/msg01031.php
http://archives.postgresql.org/pgsql-general/2009-11/msg00041.php

Alvaro Herrera committed:

- Fix longstanding problems in VACUUM caused by untimely
interruptions. In VACUUM FULL, an interrupt after the initial
transaction has been recorded as committed can cause postmaster to
restart with the following error message: PANIC: cannot abort
transaction NNNN, it was already committed This problem has been
reported many times. In lazy VACUUM, an interrupt after the table
has been truncated by lazy_truncate_heap causes other backends'
relcache to still point to the removed pages; this can cause future
INSERT and UPDATE queries to error out with the following error
message: could not read block XX of relation 1663/NNN/MMMM: read
only 0 of 8192 bytes The window to this race condition is extremely
narrow, but it has been seen in the wild involving a cancelled
autovacuum process. The solution for both problems is to inhibit
interrupts in both operations until after the respective
transactions have been committed. It's not a complete solution,
because the transaction could theoretically be aborted by some other
error, but at least fixes the most common causes of both problems.

- Support optional FROM/IN in FETCH and MOVE. The main motivation for
this is that it's required for Informix compatibility in ECPG. This
patch makes the ECPG and core grammars a bit closer to one another
for these productions. Zoltan Boszormenyi

- Document the previous FETCH and MOVE changes.

- Change "name" nonterminal in cursor-related productions to
cursor_name. This is a preparatory patch for allowing a dynamic
cursor name be used in the ECPG grammar. Zoltan Boszormenyi.

Peter Eisentraut committed:

- In pgsql/src/bin/psql/describe.c, in psql \du, separate the role
attributes by comma instead of newline, for an arguably more
pleasant display.

- In pgsql/src/backend/tsearch/wparser_def.c, make text search parser
accept underscores in XML attributes (bug #5075).

Teodor Sigaev committed:

- In pgsql/src/backend/access/gin/ginget.c, fix multicolumn GIN's
wrong results with fastupdate enabled. User-defined consistent
functions believes the check array contains at least one true
element which was not a true for scanning pending list. Per report
from Yury Don.

Heikki Linnakangas committed:

- In pgsql/src/backend/parser/parse_expr.c, when you do
"ARRAY[...]::domain", where domain is a domain over an array type,
we need to check domain constraints. We used to do it correctly, but
8.4 introduced a separate code path for the "ARRAY[]::arraytype"
case to infer the type of an empty ARRAY construct from the cast
target, and forgot to take domains into account. Per report from
Florian G. Pflug.

- In pgsql/src/backend/parser/parse_expr.c, a better fix for the
"ARRAY[...]::domain" problem. The previous patch worked, but the
transformed ArrayExpr claimed to have a return type of "domain",
even though the domain constraint was only checked by the enclosing
CoerceToDomain node. With this fix, the ArrayExpr is correctly
labeled with the base type of the domain. Per gripe by Tom Lane.

Magnus Hagander committed:

- Add inheritable ACE when creating a restricted token for execution
on Win32. Also refactor the code around it to be more clear. Jesse
Morris.

- Backpatch the inheritable-ACE patch for Win32 to 8.2 as well, except
for the pg_regress part which did not support admin execution in
8.2.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Josh Tolley sent in another revision of the patch to add in-line (DO)
functions to PL/Perl[U]. Brendan Jurd sent some cleanups for it.

Heikki Linnakangas sent in another revision of the Hot Standby patch.

Emmanuel Cecchet sent in two more revisions of the patch to add
partitioning support to COPY.

Joachim Wieland sent in a patch to add a payload to LISTEN/NOTIFY.

ITAGAKI Takahiro sent in another revision of the table partitioning
patch.

Peter Eisentraut sent in another revision of the patch for PL/PythonU
array support.

Peter Eisentraut sent in a patch to add Python 3.1 to PL/PythonU.

ITAGAKI Takahiro sent in an update version of the TRIGGER with WHEN
patch.

Andres Freund sent in another revision of the application name logging
patch.

ITAGAKI Takahiro sent in another revision of the VACUUM FULL
refactoring patch.

KaiGai Kohei sent in another revision of his SE-PostgreSQL patch.

Andrew (RhodiumToad) Gierth sent in a patch to add ORDER BY to the
inside of aggregates for the non-WINDOW context.

KaiGai Kohei sent in another revision of the patch to add ACLs for
large objects.

Zdenek Kotala sent in a patch to add dtrace probes for memory
management.

Zdenek Kotala sent in another revision of that patch to add dtrace
probe groups for executor and slru.

Andrew (RhodiumToad) Gierth sent in a doc patch for the aggregate
ORDER BY patch.

Hitoshi Harada sent in a patch to add more frame types (ROWS n
PRECEDING/FOLLOWING) to windowing frames.

George Gensure sent in a patch intended to report the schema along
with the table name on errors.

Robert Haas sent in a patch to allow you to set random_page_cost
and seq_page_cost at the granularity of tablespace.

Marko (johto) Tiikkaja sent in another revision of the Writeable CTE
patch.

Heikki Linnakangas sent in another revision of the Hot Standby patch.

Florian Pflug sent in a patch to allow inspection of rowtypes in SQL
and PL/pgsql.

Pavel Stehule sent in another revision of the function typmod patch.

ITAGAKI Takahiro sent in another revision of the VACUUM refactoring
patch.

Jeff Davis sent in another revision of the operator exclusion
constraints patch.

Roger Leigh sent in three more revisions of the Unicode formatting
patch for psql output.

Pavel Stehule sent in a patch to allow using psql variables as actual
query parameters.

ITAGAKI Takahiro sent in a review of Greg Sabino Mullane's patch to
add YAML output as an option for EXPLAIN [ANALYZE].

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - November 08 2009 ==

2009-11-08T21:16:29Z

== PostgreSQL Weekly News - November 08 2009 ==

PGDay.EU is over, with plans already rolling for next year's in the
Netherlands.

PostgreSQL 8.5alpha2 RPMs are now available. Thanks, Devrim!
http://yum.pgsqlrpms.org/howtuyum.php

== PostgreSQL Product News ==

pgtune 0.9.2, a system for tuning the base configuration file for
PostgreSQL, released.
http://pgfoundry.org/projects/pgtune/

== PostgreSQL Jobs for November ==

http://archives.postgresql.org/pgsql-jobs/2009-11/threads.php

== PostgreSQL Local ==

OpenSQL Camp will be November 14-15, 2009 in Portland, OR
http://www.chesnok.com/daily/2009/07/29/opensql-camp-comes-to-portland-november-14-15-2009/

JPUG 10th Anniversary Conference is November 20-21, 2009 in Tokyo, Japan.
http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php

Stefan Keller will be teach a course called, "Introducion to
PostGIS/PostgreSQL" at the University of Applied Sciences Rapperswil
(HSR) on January 14, 2010 in Zurich, Switzerland.
http://www.gis.hsr.ch/wiki/Agenda

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Peter Eisentraut committed:

- Fix obscure segfault condition in PL/Python In PLy_output(), when
the elog() call in the TRY branch throws an exception (this can
happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault,
because the Py_XDECREF(so) call before it releases memory that is
still used by the sv variable that PyErr_SetString() uses as
argument, because sv points into memory owned by so. Backpatched
back to 8.0, where this code was introduced. I also threw in a
couple of volatile declarations for variables that are used before
and after the TRY. I don't think they caused the crash that I
observed, but they could become issues.

- In pgsql/src/bin/psql/describe.c, show view definition only with
\d+, not with \d The rationale is that view definitions tend to be
long and obscure the main information about the view.

- Improve PL/Python elog output. When the elog functions (plpy.info
etc.) get a single argument, just print that argument instead of
printing the single-member tuple like ('foo',).

- Fix regression tests for psql \d view patch.

- Build bzip2 tarball in dist target as well.

- In pgsql/src/backend/postmaster/syslogger.c, reenable -> re-enable
Pointed out by Debian's lintian.

Heikki Linnakangas committed:

- In pgsql/src/backend/commands/tablecmds.c, allow rewriting ALTER
TABLE to skip WAL logging. Itagaki Takahiro, with small changes by
me and Simon.

- In pgsql/contrib/pg_standby/pg_standby.c, disable triggering
failover with a signal in pg_standby on Windows, because Windows
doesn't do signal processing like other platforms do. It never
really worked, but recent changes to the signal handling made it
crash. This fixes bug #4961. Patch by Fujii Masao.

Tom Lane committed:

- Add support for invoking parser callback hooks via SPI and in cached
plans. As proof of concept, modify plpgsql to use the hooks.
plpgsql is still inserting $n symbols textually, but the "back end"
of the parsing process now goes through the ParamRef hook instead of
using a fixed parameter-type array, and then execution only fetches
actually-referenced parameters, using a hook added to ParamListInfo.
Although there's a lot left to be done in plpgsql, this already
cures the "if (TG_OP = 'INSERT' and NEW.foo ...)" problem, as
illustrated by the changed regression test.

- In pgsql/src/backend/parser/gram.y, make expression locations for
LIKE and SIMILAR TO constructs uniformly point at the first keyword
of the expression, rather than drawing a rather artificial
distinction between the ESCAPE subclause and the rest. Per gripe
from Gokulakannan Somasundaram and subsequent discusssion.

- Rename some encoding conversion modules to keep pathnames in our
source tarballs under 100 characters. This should avoid failures
with certain untarring tools (WinZip and Midnight Commander have
been mentioned as likely suspects). Per my proposal of yesterday.
catversion bumped since the initial contents of pg_proc change.

- Allow binary-coercible cases in ri_HashCompareOp; there are some
such cases that are not handled by find_coercion_pathway, notably
composite->RECORD. Now that 8.4 supports composites as primary
keys, it's worth dealing with this case.

- Remove plpgsql's RENAME declaration, which has bizarre and mostly
nonfunctional behavior, and is so little used that no one has been
interested in fixing it. To ensure that possible uses are covered,
remove the ALIAS declaration's arbitrary restriction that only $n
identifiers can be aliased. (We could alternatively make RENAME act
just like ALIAS, but per discussion having two different ways to do
the same thing is probably more confusing than helpful.)

- Don't treat NEW and OLD as reserved words anymore. For the purposes
of rules it works just as well to have them be ordinary identifiers,
and this gets rid of a number of ugly special cases. Plus we aren't
interfering with non-rule usage of these names. catversion bump
because the names change internally in stored rules.

- Change plpgsql from using textual substitution to insert variable
references into SQL expressions, to using the newly added parser
callback hooks. This allows us to do the substitutions in a more
semantically-aware way: a variable reference will only be recognized
where it can validly go, ie, a place where a column value or
parameter would be legal, instead of the former behavior that would
replace any textual match including table names and column aliases
(leading to syntax errors later on). A release-note-worthy fine
point is that plpgsql variable names that match fully-reserved words
will now need to be quoted. This commit preserves the former
behavior that variable references take precedence over any possible
match to a column name. The infrastructure is in place to support
the reverse precedence or throwing an error on ambiguity, but those
behaviors aren't accessible yet. Most of the code changes here are
associated with making the namespace data structure persist so that
it can be consulted at runtime, instead of throwing it away at the
end of initial function parsing. The plpgsql scanner is still doing
name lookups, but that behavior is now irrelevant for SQL
expressions. A future commit will deal with removing unnecessary
lookups.

- Rearrange plpgsql parsing to simplify and speed it up a bit. 1.
Pull the responsibility for %TYPE and %ROWTYPE out of the scanner,
letting read_datatype manage it instead. 2. Avoid unnecessary
scanner-driven lookups of plpgsql variables in places where it's not
needed, which is actually most of the time; we do not need it in
DECLARE sections nor in text that is a SQL query or expression. 3.
Rationalize the set of token types returned by the scanner:
distinguishing T_SCALAR, T_RECORD, T_ROW seems to complicate the
grammar in more places than it simplifies it, so merge these into
one token type T_DATUM; but split T_ERROR into T_DBLWORD and
T_TRIPWORD for clarity and simplicity of later processing. Some of
this will need to be revisited again when we try to make plpgsql use
the core scanner, but this patch gets some of the bigger stumbling
blocks out of the way.

- Remove ancient text file containing plpgsql installation
instructions. This was long ago superseded by the standard build
process and main SGML documentation.

- Modernize plpgsql's handling of parse locations, making it look a
lot more like the core parser's code. In particular, track
locations at the character rather than line level during parsing,
allowing many more parse-time error conditions to be reported with
precise error pointers rather than just "near line N". Also,
exploit the fact that we no longer need to substitute $N for
variable references by making extracted SQL queries and expressions
be exact copies of subranges of the function text, rather than
having random whitespace changes within them. This makes it
possible to directly map parse error positions from the core parser
onto positions in the function text, which lets us report them
without the previous kluge of showing the intermediate
internal-query form. (Later it might be good to do that for core
parse-analysis errors too, but this patch is just touching plpgsql's
lexer/parser, not what happens at runtime.) In passing, make
plpgsql's lexer use palloc not malloc. These changes make plpgsql's
parse-time error reports noticeably nicer (as illustrated by the
regression test changes), and will also simplify the planned removal
of plpgsql's separate lexer by reducing the impedance mismatch
between what it does and what the core lexer does.

- Fix WHERE CURRENT OF to work as designed within plpgsql. The
argument can be the name of a plpgsql cursor variable, which
formerly was converted to $N before the core parser saw it, but
that's no longer the case. Deal with plain name references to
plpgsql variables, and add a regression test case that exposes the
failure.

Andrew Dunstan committed:

- Keep track of language's trusted flag in InlineCodeBlock. Needed to
support DO blocks for languages that have both trusted and untrusted
variants.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Josh Tolley and Andrew Dunstan make call-and-response patches to allow
PL/Perl[U] to have in-line (DO) functions.

Pavel Stehule sent in two revisions of a patch to make it possible to
store the typemods for function parameters, both input and output.

Peter Eisentraut sent in a patch to support arrays in PL/PythonU as
both input and output parameters.

John Naylor sent in a WIP patch to move the current BKI system to one
where one set of files drives the creation of both the bootstrap files
and some hard-coded strings in header files from YAML formatted
descriptions of the system catalogs.

ITAGAKI Takahiro sent in another WIP patch to do partitioning range
and list partitioning directly in SQL.

KaiGai Kohei sent in a patch to disallow renaming a column inherited
from multiple parents.

Alvaro Herrera sent in a WIP patch to fix a corner case where VACUUM
and TRUNCATE don't work together correctly.

Jeff Davis sent in two more revisions of the operator exclusion
constraints patch.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Free VPS Hosting w/ PostgreSQL - Limited Availability

2009-11-05T18:23:56Z

Starting this month (ie. effective right now), we are giving away *10*
Free Starter VPSs each month. Purely on a first come, first serve basis,
once all 10 are gone, they are gone until the 1st day of the next month.

This is *not* cPanel hosting ... this is a true VPS, with full shell
access, and root.

To grab them up is simple:

Go to http://ams.hub.org/signup
Fill in the form and:

Choose the *Annual Starter Package*
Enter the word "FreeHosting" for the Coupon Field.

and that is it.

The process will confirm your email address, after which it will be
auto-activated and ready for you to use.

This is only applicable to the *Annual Starter*.

It runs just like any other Starter account, you just don't have to pay
for the *First Year* of service on it, but you are responsible for any
form of overusage that the account does accrue.

And spread the word ...

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy@... http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@...

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PostgreSQL 8.5 Alpha2 RPMs released.

2009-11-05T14:55:32Z

Hi,

PostgreSQL RPM Building Project released RPM sets for 2nd Alpha of the
upcoming 8.5 release.

Please note that these packages are **not** production ready. They are
for Fedora 7,8,9,11 and RHEL/CentOS 4,5.

These packages *do* require a dump/reload, even from the first alpha
packages, because of catversion updates.

We need more people to discover any bugs and test new features in 8.5
development version.

Here is the list of the new features in 8.5 development version:

http://developer.postgresql.org/pgdocs/postgres/release-8-5.html

This RPM set has new experimental feature that has been requested for a
long time: Multiple version installation for RPMs.

As usual, please find detailed info about RPMs from:

http://yum.pgsqlrpms.org/howtuyum.php

A mini howto about 8.5 alpha release2 + RPMs are here:

http://yum.pgsqlrpms.org/news-8.5alpha-packages-ready-for-testing.php

Please report any packaging related errors to me. If you find any
PostgreSQL 8.5 bugs, please post them to pgsql-bugs@... or
fill out this form:

http://www.postgresql.org/support/submitbug

Sincerely,
--
Devrim GÜNDÜZ, RHCE
Command Prompt - http://www.CommandPrompt.com
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz

signature.asc (204 bytes) Download Attachment

== PostgreSQL Weekly News - November 01 2009 ==

2009-11-02T01:21:28Z

== PostgreSQL Weekly News - November 01 2009 ==

PostgreSQL 8.5alpha2 released. Start testing those apps in your test
environment!
http://www.postgresql.org/developer/alpha

== PostgreSQL Product News ==

pgtune 0.9.2, a system for tuning the base configuration file for
PostgreSQL, released.
http://pgfoundry.org/projects/pgtune/

== PostgreSQL Local ==

LISA 09, the Large Installation and Systems Administration conference,
will be held November 1-6, 2009. There will be a Postgres booth
Wednesday and Thursday.
http://www.usenix.org/event/lisa09/

PGDay.EU 2009 will be at Telecom ParisTech in Paris, France on
November 6-7, 2009.
http://www.pgday.eu/

OpenSQL Camp in Portland is looking for sponsors. Make your travel plans now! :)
http://www.chesnok.com/daily/2009/07/29/opensql-camp-comes-to-portland-november-14-15-2009/

JPUG 10th Anniversary Conference is November 20-21, 2009 in Tokyo, Japan.
http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Heikki Linnakangas committed:

- Fix range check in date_recv that tried to limit accepted values to
only those accepted by date_in(). I confused Julian day numbers and
number of days since the postgres epoch 2000-01-01 in the original
patch. I just noticed that it's still easy to get such out-of-range
values into the database using to_date or +- operators, but this
patch doesn't do anything about those functions. Per report from
James Pye.

Peter Eisentraut committed:

- In pgsql/src/test/regress/GNUmakefile, check errors in for loop.

- Simplify a few makefile rules since install-sh can now install
multiple files in one run.

- In pgsql/GNUmakefile.in, remove some leftovers of split tarball
support.

Alvaro Herrera committed:

- In pgsql/doc/src/sgml/ref/create_table.sgml, fix documentation on
the toast.fillfactor reloption: it doesn't exist. Per note from
Zoltan Boszormenyi.

Tom Lane committed:

- Make FOR UPDATE/SHARE in the primary query not propagate into WITH
queries; for example in WITH w AS (SELECT * FROM foo) SELECT * FROM
w, bar ... FOR UPDATE the FOR UPDATE will now affect bar but not
foo. This is more useful and consistent than the original 8.4
behavior, which tried to propagate FOR UPDATE into the WITH query
but always failed due to assorted implementation restrictions. Even
though we are in process of removing those restrictions, it seems
correct on philosophical grounds to not let the outer query's FOR
UPDATE affect the WITH query. In passing, fix isLockedRel which
frequently got things wrong in nested-subquery cases: "FOR UPDATE OF
foo" applies to an alias foo in the current query level, not
subqueries. This has been broken for a long time, but it doesn't
seem worth back-patching further than 8.4 because the actual
consequences are minimal. At worst the parser would sometimes get
RowShareLock on a relation when it should be AccessShareLock or vice
versa. That would only make a difference if someone were using
ExclusiveLock concurrently, which no standard operation does, and
anyway FOR UPDATE doesn't result in visible changes so it's not
clear that the someone would notice any problem. Between that and
the fact that FOR UPDATE barely works with subqueries at all in
existing releases, I'm not excited about worrying about it.

- In pgsql/src/backend/commands/trigger.c, fix AfterTriggerSaveEvent
to use a test and elog, not just Assert, to check that it's called
within an AfterTriggerBeginQuery/AfterTriggerEndQuery pair. The RI
cascade triggers suppress that overhead on the assumption that they
are always run non-deferred, so it's possible to violate the
condition if someone mistakenly changes pg_trigger to mark such a
trigger deferred. We don't really care about supporting that, but
throwing an error instead of crashing seems desirable. Per report
from Marcelo Costa.

- When FOR UPDATE/SHARE is used with LIMIT, put the LockRows plan node
underneath the Limit node, not atop it. This fixes the old problem
that such a query might unexpectedly return fewer rows than the
LIMIT says, due to LockRows discarding updated rows. There is a
related problem that LockRows might destroy the sort ordering
produced by earlier steps; but fixing that by pushing LockRows below
Sort would create serious performance problems that are unjustified
in many real-world applications, as well as potential deadlock
problems from locking many more rows than expected. Instead, keep
the present semantics of applying FOR UPDATE after ORDER BY within a
single query level; but allow the user to specify the other way by
writing FOR UPDATE in a sub-select. To make that work, track
whether FOR UPDATE appeared explicitly in sub-selects or got pushed
down from the parent, and don't flatten a sub-select that contained
an explicit FOR UPDATE.

- Fix AcquireRewriteLocks to be sure that it acquires the right lock
strength when FOR UPDATE is propagated down into a sub-select
expanded from a view. Similar bug to parser's isLockedRel issue
that I fixed yesterday; likewise seems not quite worth the effort to
back-patch.

- In pgsql/src/bin/psql/describe.c, fix \df to re-allow regexp special
characters in the function name pattern. This has always worked, up
until somebody's thinko here:
http://archives.postgresql.org/pgsql-committers/2009-04/msg00233.php
Per bug #5143 from Piotr Wolinski.

- In pgsql/src/backend/utils/adt/ruleutils.c, un-break EXPLAIN for
Append plans. I messed this up a few days ago while adding the
ModifyTable node type --- I had been thinking ModifyTable should
replace Append as a special case in push_plan(), but actually both
of them have to be special-cased.

- In pgsql/src/backend/executor/nodeHash.c, make the overflow guards
in ExecChooseHashTableSize be more protective. The original coding
ensured nbuckets and nbatch didn't exceed INT_MAX, which while not
insane on its own terms did nothing to protect subsequent code like
"palloc(nbatch * sizeof(BufFile *))". Since enormous join size
estimates might well be planner error rather than reality, it seems
best to constrain the initial sizes to be not more than
work_mem/sizeof(pointer), thus ensuring the allocated arrays don't
exceed work_mem. We will allow nbatch to get bigger than that
during subsequent ExecHashIncreaseNumBatches calls, but we should
still guard against integer overflow in those palloc requests. Per
bug #5145 from Bernt Marius Johnsen. Although the given test case
only seems to fail back to 8.2, previous releases have variants of
this issue, so patch all supported branches.

- Implement parser hooks for processing ColumnRef and ParamRef nodes,
as per my recent proposal. As proof of concept, remove knowledge of
Params from the core parser, arranging for them to be handled
entirely by parser hook functions. It turns out we need an
additional hook for that --- I had forgotten about the code that
handles inferring a parameter's type from context. This is a
preliminary step towards letting plpgsql handle its variables
through parser hooks. Additional work remains to be done to expose
the facility through SPI, but I think this is all the changes needed
in the core parser.

- In pgsql/src/pl/plperl/plperl.c, ensure the previous Perl
interpreter selection is restored upon exit from
plperl_call_handler, in both the normal and error-exit paths. Per
report from Alexey Klyukin.

- Fix two serious bugs introduced into hash indexes by the 8.4 patch
that made hash indexes keep entries sorted by hash value. First,
the original plans for concurrency assumed that insertions would
happen only at the end of a page, which is no longer true; this
could cause scans to transiently fail to find index entries in the
presence of concurrent insertions. We can compensate by teaching
scans to re-find their position after re-acquiring read locks.
Second, neither the bucket split nor the bucket compaction logic had
been fixed to preserve hashvalue ordering, so application of either
of those processes could lead to permanent corruption of an index,
in the sense that searches might fail to find entries that are
present. This patch fixes the split and compaction logic to
preserve hashvalue ordering, but it cannot do anything about
pre-existing corruption. We will need to recommend reindexing all
hash indexes in the 8.4.2 release notes. To buy back the
performance loss hereby induced in split and compaction, fix them to
use PageIndexMultiDelete instead of retail PageIndexDelete
operations. We might later want to do something with qsort'ing the
page contents rather than doing a binary search for each insertion,
but that seemed more invasive than I cared to risk in a back-patch.
Per bug #5157 from Jeff Janes and subsequent investigation.

- Department of second thoughts: after studying index_getnext() a bit
more I realize that it can scribble on scan->xs_ctup.t_self while
following HOT chains, so we can't rely on that to stay valid between
hashgettuple() calls. Introduce a private variable in
HashScanOpaque, instead.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Michael Paquier sent in another revision of the patch to allow pgbench
to issue shell commands.

ITAGAKI Takahiro sent in another patch to add VACUUM ( FULL [ INPLACE
| REPLACE ] ).

Jeff Davis sent in two more revisions of the operator exclusion
constraints patch.

Peter Eisentraut sent in a patch to make \d+ work better for views in
psql.

Shrish Purohit sent in a patch intended to automate partitioning.

Peter Eisentraut sent in a patch to fix an issue where PL/PythonU can
segfault.

Peter Eisentraut sent in a patch to fix an issue with PL/PythonU's
elog output.

Roger Leigh sent in another patch to make an "ascii clean" format for
psql output.

Hitoshi Harada sent in a patch which implements PL/Javascript using
Google's V8 Javascript engine.

ITAGAKI Takahiro sent in a WIP patch to implement table partitioning
in SQL.

Andreas Freund sent in a patch which makes certain tsearch operations
more efficient.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - October 25 2009 ==

2009-10-25T20:55:55Z

== PostgreSQL Weekly News - October 25 2009 ==

== PostgreSQL Product News ==

once:fabrik, an ERP system based on PostgreSQL, is available for a
free trial until October 31, 2009.
http://www.oncetechnologies.com/

== PostgreSQL Jobs for October ==

http://archives.postgresql.org/pgsql-jobs/2009-10/threads.php

== PostgreSQL Local ==

LISA 09, the Large Installation and Systems Administration conference,
will be held November 1-6, 2009. There will be a Postgres booth
Wednesday and Thursday.
http://www.usenix.org/event/lisa09/

PGDay.EU 2009 will be at Telecom ParisTech in Paris, France on
November 6-7, 2009. Registration is open.
http://www.pgday.eu/

OpenSQL Camp in Portland is looking for sponsors. Make your travel plans now! :)
http://www.chesnok.com/daily/2009/07/29/opensql-camp-comes-to-portland-november-14-15-2009/

JPUG 10th Anniversary Conference is November 20-21, 2009 in Tokyo, Japan.
http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Peter Eisentraut committed:

- In pgsql/src/tools/RELEASE_CHANGES, update translation updating
procedure. This pertains to some changes I made to automatically
exclude translations below the 80% minimum.

- Translations update for 8.5alpha2

- In pgsql/doc/src/sgml/release-8.5.sgml, preliminary release notes
for 8.5alpha2.

- In pgsql/doc/src/sgml/release-8.5.sgml, finalize 8.5alpha2 release
notes, with updates from Josh Berkus.

- Version stamp 8.5alpha2.

- When querying a table with child tables, do not check permissions on
the child tables. This was found to be useless and confusing in
virtually all cases, and also contrary to the SQL standard.

Tom Lane committed:

- Remove add_missing_from GUC and associated parser support for
"implicit RTEs". Per recent discussion, add_missing_from has been
deprecated for long enough to consider removing, and it's getting in
the way of planned parser refactoring. The system now always
behaves as though add_missing_from were OFF.

- Remove regex_flavor GUC, so that regular expressions are always
"advanced" style by default. Per discussion, there seems to be
hardly anything that really relies on being able to change the regex
flavor, so the ability to select it via embedded options ought to be
enough for any stragglers. Also, if we didn't remove the GUC, we'd
really be morally obligated to mark the regex functions
non-immutable, which'd possibly create performance issues.

- Re-implement EvalPlanQual processing to improve its performance and
eliminate a lot of strange behaviors that occurred in join cases.
We now identify the "current" row for every joined relation in
UPDATE, DELETE, and SELECT FOR UPDATE/SHARE queries. If an
EvalPlanQual recheck is necessary, we jam the appropriate row into
each scan node in the rechecking plan, forcing it to emit only that
one row. The former behavior could rescan the whole of each joined
relation for each recheck, which was terrible for performance, and
what's much worse could result in duplicated output tuples. Also,
the original implementation of EvalPlanQual could not re-use the
recheck execution tree --- it had to go through a full executor init
and shutdown for every row to be tested. To avoid this overhead,
I've associated a special runtime Param with each LockRows or
ModifyTable plan node, and arranged to make every scan node below
such a node depend on that Param. Thus, by signaling a change in
that Param, the EPQ machinery can just rescan the already-built test
plan. This patch also adds a prohibition on set-returning functions
in the targetlist of SELECT FOR UPDATE/SHARE. This is needed to
avoid the duplicate-output-tuple problem. It seems fairly
reasonable since the other restrictions on SELECT FOR UPDATE are
meant to ensure that there is a unique correspondence between source
tuples and result tuples, which an output SRF destroys as much as
anything else does.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Dave Page sent in two more revisions of the patch to make the
connecting application name available for display and modification via
a GUC.

Dean Rasheed sent in a WIP patch to scale up deferred UNIQUE
constraints.

ITAGAKI Takahiro sent in a patch to implement a process utility hook.

ITAGAKI Takahiro sent in a patch to allow psql to and use Byte Order
Marks.

ITAGAKI Takahiro sent in another revision of a patch which adds the
option to add an SQL:2008-compliant WHEN clause to trigger
definitions.

Marko (johto) Tiikkaja sent in a WIP patch implementing writeable
CTEs.

ITAGAKI Takahiro sent in a WIP patch to make VACUUM FULL unneeded

Magnus Hagander sent in a patch to parse all configuration files in a
directory. This is, among other things, infrastructure for tools
which could manipulate such files.

Roger Leigh sent in three more revisions of the Unicode pretty-print
patch for psql.

Jeff Davis sent in another revision of the operator exclusion
constraints patch.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PostgreSQL 8.5alpha2 Now Available

2009-10-24T10:44:14Z

The second alpha release for PostgreSQL version 8.5, 8.5alpha2, is now
available. This alpha contains several new major features added since
the previous alpha. Please download, install, and test it to give us
early feedback on the features being developed for the next version of
PostgreSQL.

Features added in Alpha2 include:

* DEFAULT PRIVILEGES and GRANT ALL ON to give DBAs easier management of
object permissions in their databases
* The DO statement so that you can run ad-hoc procedural language code
on the SQL command line
* Triggers on columns
* Named parameters in function calls
* Improved HStore, making this exotic type far more useful to
application developers
* Multiple administration and performance improvements

These new major features mean that we need you to participate in testing
them. If you are able to help with organized alpha testing, please see
the Alpha/Beta testing page:
http://wiki.postgresql.org/wiki/HowToBetaTest

Alphas are not stable and should never be used in production; they are
for testing new features only. There will be two more alphas, about
every 2 months, before an 8.5 beta release. There is no guarantee that
any features or APIs present in the alphas will be present, or the same,
in the final release.

More detail is available in the Release Notes included with each alpha:
http://developer.postgresql.org/pgdocs/postgres/release-8.5.html

Alpha information page:
http://www.postgresql.org/developer/alpha

Download the alpha here:
http://www.postgresql.org/ftp/source/8.5alpha2/

Alpha2 is currently available in source code form only. Binary packages
for some operating systems will be prepared in the coming days.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PgUS Board Nominations Now Open

2009-10-22T10:29:11Z

Greetings! We are now accepting nominations for the United States
PostgreSQL Association (PgUS) board for the Fall 2009 elections;
please submit nominations (full name and a contact email address,
please) to:

secretary@...

I will contact the nominees (to see if they accept the nomination) and
report weekly to pgus-general the list of current nominees.

Nominations will close on November 2nd.

We have three seats available, currently being held by Michael Brewer,
Joshua Drake, and Bruce Momjian.

Per our bylaws, you'll need to be a member of PgUS to vote.

https://www.postgresql.us/join

Please let me know if you have any questions; get those nominations in ASAP!

Thanks---
---Michael Brewer
Secretary, PgUS
secretary@...
mbrewer@...

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PGDay.EU 2009 - registration deadline extended

2009-10-22T08:32:53Z

I'm pleased to announce that the registration deadline for PGDay.EU
2009 on November 6th & 7th in Paris has been extended to the 31st
October, allowing attendees an extra eight days to benefit from the
cheapest pricing. Attendees registering after the 31st October will be
charged the 'on the door' price.

This is possible thanks to the generous support of our sponsors:

http://2009.pgday.eu/sponsors

For more information on the conference, including the talk schedule
and registration and travel information, please visit the website at:

http://2009.pgday.eu/

See you in Paris!

--
Dave Page
PGDay.EU 2009 Conference: http://2009.pgday.eu/

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Re: [pgeu-general] PGDay.EU 2009 - approaching fast!

2009-10-21T14:50:55Z

I've put the English schedule (Désolé utilisateurs Français) on a
calendar for my own use, but made it public in case anyone else might
find it helpful, like syncing it with a mobile device etc:

XML: http://www.google.com/calendar/feeds/dp7jfelvcbtmks1m021c6rt3dk@.../public/basic

iCal: http://www.google.com/calendar/ical/dp7jfelvcbtmks1m021c6rt3dk@.../public/basic.ics

By the way, does anyone have a Time Turner
(http://en.wikipedia.org/wiki/Time_Turner#Time-Turners) they can loan
to me for this event? ;)

Thom

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PostgreSQL Conference 2009 Japan : Schedule available and registration open

2009-10-21T08:10:09Z

PostgreSQL Conference 2009 Japan announcement

　　　　　　　　　　　　　　　　　　　　　　　21 Octover 2009, Tokyo

The PostgreSQL Conference 2009 Tokyo Executive Committee are proud to
announce that the two days programme sessions, JPUG 10th Anniversary
Conference, are going to be held on 20th and 21st November, 2009, at AM
Hamamatsucho, Tokyo.

Please see the Website at
http://www.postgresql.jp/events/pgcon09j/e/pgcon2009j/view
for the general information and its programmes, as well as
http://wiki.postgresql.jp/pgcon2009j/Registration
for your registration.

The PostgreSQL Cluster Developers' Meeting is also scheduled one day
before the conference, namely, 19th November for PostgreSQL global
developers to discuss PostgreSQL clustering and replication issues.
Please also vist
http://www.postgresql.jp/events/pgcon09j/e/dev_mtg
to know what it will be.

See you in Tokyo.

Kaori INABA
Chairperson of The Committee

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Re: [pgeu-general] PGDay.EU 2009 - approaching fast!

2009-10-20T04:52:41Z

2009/10/20 Dave Page <dpage@...>:

> PGDay.EU 2009 is approaching fast - have you registered yet?
>
> Europe's premier PostgreSQL conference organised by PostgreSQL Europe
> and PostgreSQLfr will be held on November 6th and 7th at ParisTech
> Telecom in Paris, France. With an outstanding lineup of talks over the
> two days of the event, with tracks in English and French, this is the
> must-attend PostgreSQL conference this year!
>
> http://2009.pgday.eu/start
>
> Speakers will include well known community members and developers such
> as Simon Riggs, Gavin M. Roy, Gabriele Bartolini, Dimitri Fontaine,
> Joshua Drake and Guillaume Lelarge speaking on a wide range of topics.
> The full schedule can be seen at http://2009.pgday.eu/schedule
>
> If you are planning on attending, please register as soon as possible
> at http://2009.pgday.eu/register. Early registration will help us
> ensure you get a T-Shirt and conference goodies!
>
> Details of the venue and hotels in the local area can also be found on
> the conference website. If you have yet to book your accommodation, I
> would suggest doing so as soon as possible as Paris is quite busy at
> this time of year.

And there's special hotel rates at the Kyriad Hotel, in Porte d'Ivry
for those attending the conference. See http://2009.pgday.eu/hotels
for details.

Thom

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PGDay.EU 2009 - approaching fast!

2009-10-20T04:14:28Z

PGDay.EU 2009 is approaching fast - have you registered yet?

Europe's premier PostgreSQL conference organised by PostgreSQL Europe
and PostgreSQLfr will be held on November 6th and 7th at ParisTech
Telecom in Paris, France. With an outstanding lineup of talks over the
two days of the event, with tracks in English and French, this is the
must-attend PostgreSQL conference this year!

http://2009.pgday.eu/start

Speakers will include well known community members and developers such
as Simon Riggs, Gavin M. Roy, Gabriele Bartolini, Dimitri Fontaine,
Joshua Drake and Guillaume Lelarge speaking on a wide range of topics.
The full schedule can be seen at http://2009.pgday.eu/schedule

If you are planning on attending, please register as soon as possible
at http://2009.pgday.eu/register. Early registration will help us
ensure you get a T-Shirt and conference goodies!

Details of the venue and hotels in the local area can also be found on
the conference website. If you have yet to book your accommodation, I
would suggest doing so as soon as possible as Paris is quite busy at
this time of year.

See you in Paris!

--
Dave Page
PGDay.EU 2009 Conference: http://2009.pgday.eu/start

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

== PostgreSQL Weekly News - October 18 2009 ==

2009-10-18T18:41:29Z

== PostgreSQL Weekly News - October 18 2009 ==

Commitfest 2009-09 is now over. You can all start working on your own
patches now :)

PostgreSQL Conference (JDCon) West closed out today. Thanks to all
the wonderful people in Seattle for making it a success.

== PostgreSQL Product News ==

PWN Translator 3.0, a translation script for the PostgreSQL Weekly
News, released.
http://pgfoundry.org/projects/pwn-translation/

Benetl 3.2, an ETL tool for files using PostgreSQL, released.
http://www.benetl.net

Bucardo 4.3.0, a replication system with dual-master capability, released.
http://bucardo.org/wiki/Bucardo

== PostgreSQL Jobs for October ==

http://archives.postgresql.org/pgsql-jobs/2009-10/threads.php

== PostgreSQL Local ==

PGCon Brazil will be take place October 23-24 2009 at Unicamp in
Campinas, Sao Paulo state. Registration open!
http://pgcon.postgresql.org.br/2009/

Federico Campoli will be presenting a PostgreSQL talk at GULP (Linux
Day Pisa) on October 24, 2009. Information in Italian below:
http://linuxday2009.gulp.linux.it/

PGDay.EU 2009 will be at Telecom ParisTech in Paris, France on
November 6-7, 2009. Registration is open.
http://www.pgday.eu/

OpenSQL Camp in Portland is looking for sponsors. Make your travel plans now! :)
http://www.chesnok.com/daily/2009/07/29/opensql-camp-comes-to-portland-november-14-15-2009/

JPUG 10th Anniversary Conference is November 20-21, 2009 in Tokyo, Japan.
http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php

FOSDEM 2010 will be in Brussels, Belgium on February 6-7, 2010.
http://www.fosdem.org/

Chemnitzer Linuxtage will be in Chemnitz, Germany on March 13-14, 2010.
http://chemnitzer.linux-tage.de/

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david@..., German language
to pwn@..., Italian language to pwn@....

== Applied Patches ==

Tom Lane committed:

- Move the handling of SELECT FOR UPDATE locking and rechecking out of
execMain.c and into a new plan node type LockRows. Like the recent
change to put table updating into a ModifyTable plan node, this
increases planning flexibility by allowing the operations to occur
below the top level of the plan tree. It's necessary in any case to
restore the previous behavior of having FOR UPDATE locking occur
before ModifyTable does. This partially refactors EvalPlanQual to
allow multiple rows-under-test to be inserted into the EPQ machinery
before starting an EPQ test query. That isn't sufficient to fix
EPQ's general bogosity in the face of plans that return multiple
rows per test row, though. Since this patch is mostly about getting
some plan node infrastructure in place and not about fixing
ten-year-old bugs, I will leave EPQ improvements for another day.
Another behavioral change that we could now think about is doing FOR
UPDATE before LIMIT, but that too seems like it should be treated as
a followon patch.

- Support GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA.
Petr Jelinek

- Use plurals (TABLES, FUNCTIONS, etc) in ALTER DEFAULT PRIVILEGES.
We have the keywords as a consequence of the GRANT ALL patch, so we
might as well use them and make the ALTER commands read more
naturally.

- Code review for LIKE INCLUDING patch --- clean up some cosmetic and
not so cosmetic stuff.

- In pgsql/src/backend/utils/adt/tsvector_op.c, fix ts_stat's failure
on empty tsvector. Also insert a couple of Asserts that check for
stack overflow. Bogus coding appears to be new in 8.4 --- older
releases had a much simpler algorithm here. Per bug #5111.

- Add "\pset linestyle ascii/unicode" option to psql, allowing our
traditional ASCII-art style of table output to be upgraded to use
Unicode box drawing characters if desired. By default, psql will
use the Unicode characters whenever client_encoding is UTF8. The
patch forces linestyle=ascii in pg_regress usage, ensuring we don't
break the regression tests in Unicode locales. Roger Leigh.

- Support SQL-compliant triggers on columns, ie fire only if certain
columns are named in the UPDATE's SET list. Note: the schema of
pg_trigger has not actually changed; we've just started to use a
column that was there all along. catversion bumped anyway so that
this commit is included in the history of potentially interesting
changes to system catalog contents. Itagaki Takahiro.

- In pgsql/src/pl/plpython/expected/plpython_unicode_0.out, first
committed version of plpython_unicode_0.out did not actually contain
the required \200 bytes. Let's see if this commit works, or if CVS
is messing it up.

- In pgsql/src/backend/libpq/auth.c, rewrite pam_passwd_conv_proc to
be more robust: avoid assuming that the pam_message array contains
exactly one PAM_PROMPT_ECHO_OFF message. Instead, deal with however
many messages there are, and don't throw error for PAM_ERROR_MSG and
PAM_TEXT_INFO messages. This logic is borrowed from openssh 5.2p1,
which hopefully has seen more real-world PAM usage than we have.
Per bug #5121 from Ryan Douglas, which turned out to be caused by
the conv_proc being called with zero messages. Apparently that is
normal behavior given the combination of Linux pam_krb5 with MS
Active Directory as the domain controller. Patch all the way back,
since this code has been essentially untouched since 7.4.
(Surprising we've not heard complaints before.)

Andrew Dunstan committed:

- CREATE LIKE INCLUDING COMMENTS and STORAGE, and INCLUDING ALL
shortcut. Itagaki Takahiro.

Alvaro Herrera committed:

- Add new PGC_S_DATABASE_USER enum value to several places missed by
my patch last week. Per note and patch from Jeff Davis.

- Avoid using trivial usernames in foreign_data regression test.
Martin Pihlak.

Peter Eisentraut committed:

- In pgsql/doc/src/sgml/func.sgml, replace unmatched " by " to
avoid throwing off syntax highlighters.

- Add alternative expected file for unicode test for client encoding
not UTF8.

- In the configure check for the Python distutils module, use a less
obscure shell construct to hide away the stderr output. Python 3.1
actually core dumps on the current invocation
(http://bugs.python.org/issue7111), but the new version also has the
more general advantage of saving the error message in config.log for
analysis.

Heikki Linnakangas committed:

- In pgsql/src/backend/libpq/auth.c, raise the maximum authentication
token (Kerberos ticket) size in GSSAPI and SSPI athentication
methods. While the old 2000 byte limit was more than enough for Unix
Kerberos implementations, tickets issued by Windows Domain
Controllers can be much larger. Ian Turner.

- In pgsql/src/backend/libpq/auth.c, rename the new
MAX_AUTH_TOKEN_LENGTH #define to PG_MAX_AUTH_MAX_TOKEN_LENGTH, to
make it more obvious that it's a PostgreSQL internal limit, not
something that comes from system header files.

- In pgsql/src/bin/scripts/vacuumdb.c, FREEZE and VERBOSE options were
in wrong order in the VACUUM command that vacuumdb produces. Per
report by Thom Brown.

Michael Meskes committed:

- Made ECPG more robust against applications freeing strings, based on
patch send in by Zoltan Boszormenyi.

Magnus Hagander committed:

- Write to the Windows eventlog in UTF16, converting the message
encoding as necessary. Itagaki Takahiro with some changes from me.

- In pgsql/src/backend/utils/mb/mbutils.c, fix typo in previous
release as reported by Itagaki Takahiro, but missed by me.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Laurenz Albe sent in another revision of the patch to create a hook to
test password cryptgraphic strength along with a contrib module to use
the hook.

ITAGAKI Takahiro sent in another revision of the patch to fix encoding
issues and eventlog on Win32.

KaiGai Kohei sent in another revision of the patch for large object
ACLs.

Dave Page sent in a WIP patch to add an application_name GUC which
optionally shows the name of the connecting application.

Peter Eisentraut sent in an updated version of the per-column trigger
patch.

KaiGai Kohei sent in another revision of the ACL rework patch.

ITAGAKI Takahiro sent in another revision of the per-column trigger
patch.

Zoltan Boszormenyi sent a patch that makes ECPG more robust against
applications that free() strings by storing its own copy of the
prepared statement name.

ITAGAKI Takahiro sent in a patch to prevent table rewrites caused by
ALTER TABLE from writing WALs.

Heikki Linnakangas sent in an updated patch for Hot Standby.

ITAGAKI Takahiro sent in a patch for contrib/auto_explain which adds
EXPLAIN (ANALYZE|BUFFERS).

ITAGAKI Takahiro sent in a WIP patch to add WHEN to triggers.

Dave Page sent in another revision of the patch to add an
application_name GUC and supporting features for same.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

Re: PWN Translator 3.0

2009-10-18T06:39:19Z

On Sat, 17 Oct 2009 21:55:37 +0200 Andreas 'ads' Scherbaum wrote:

> The first public release of the translation script for the PostgreSQL
> weekly newsletter is available now. The script is intended to help
> anyone who wants to translate the english newsletter into his foreign
> language.

s/foreign/native/

Thanks to anyone who pointed this out.

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

PGDay.eu 2009 in Paris, Nov. 6/7, http://www.pgday.eu/

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...

PWN Translator 3.0

2009-10-17T12:55:37Z

The first public release of the translation script for the PostgreSQL
weekly newsletter is available now. The script is intended to help
anyone who wants to translate the english newsletter into his foreign
language.

All static content is translated using a configuration file, the
"local" and "products" section is translated using two textfiles
containing the original and translated texts. It's even possible to
handle partially changed text, like an earlier translated product news,
where only the version number has changed. The translated newsletter is
send to a configured email address.

Project website: http://pgfoundry.org/projects/pwn-translation/
Download: http://pgfoundry.org/frs/?group_id=1000397

More detailed info:
http://andreas.scherbaum.la/blog/archives/610-Making-life-easy-for-new-and-old-PWN-translators.html

Hopefully this helps to translate the PG newsletter in more languages.

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

PGDay.eu 2009 in Paris, Nov. 6/7, http://www.pgday.eu/

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

pgsql-announce-unsubscribe@...