[HACKERS] PGCon 2017 registration now open

[Dan Langille]

Join us in Ottawa for the 11th annual PGCon.  On May 23-26, users and 
developers from 
around the world arrive for what has become a traditional gathering of the 
PostgreSQL
community.

There will be two days of tutorials on Tuesday and Wednesday.  The best of the 
best 
will be available to help you learn great things about PostgreSQL and its tools.
See http://www.pgcon.org/2017/schedule/track/Tutorial/index.en.html 
<http://www.pgcon.org/2017/schedule/track/Tutorial/index.en.html>

On Wednesday, there will be a Developer Unconference (non-developers are 
welcome 
too).  The Unconference first appeared at PGCon 2013 and was a instant success.
See https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Unconference 
<https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Unconference>

For Thursday and Friday, the submitted talks will be presented as everyone 
gathers in 
one location to learn, discuss, and collaborate.

Full list of talks: http://www.pgcon.org/2017/schedule/events.en.html 
<http://www.pgcon.org/2017/schedule/events.en.html>

In summary:

• Tutorials: 23-34 May 2017 (Tue & Wed)
• Unconference: 24 May 2016
• Talks: 25-26 May 2016 (Thu-Fri).

Registration is now open at http://www.pgcon.org/2017/registration.php 
<http://www.pgcon.org/2017/registration.php>

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org <mailto:d...@langille.org>

[HACKERS] potential hardware donation

[Dan Langille]

If someone wanted to donate a SuperServer 6028TR-D72R 
(http://www.supermicro.com/products/system/2U/6028/SYS-6028TR-D72R.cfm) to the 
PostgreSQL project, would it be used?

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org

[HACKERS] reminder: PGCon 2017 CFP

[Dan Langille]

Hello,

There are two days left in the PGCon 2017 CFP, which closes on 19 January.
Please get your submissions in soon.

PGCon 2017 will be on 23-26 May 2017 at University of Ottawa.

* 23-24 (Tue-Wed) tutorials
* 24 (Wed) The Unconference
* 25-26 (Thu-Fri) talks - the main part of the conference

See http://www.pgcon.org/2017/ <http://www.pgcon.org/2017/>


We are now accepting proposals for the main part of the conference (25-26 May).
Proposals can be quite simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2016 Proposal acceptance begins
19 Jan 2017 Proposal acceptance ends
19 Feb 2017 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

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

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

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org <mailto:d...@langille.org>

[HACKERS] PGCon 2016 CFP - one week left

[Dan Langille]

Hello

There is one week left in the PGCon CFP.  Details below.  Please submit.  
Thanks.

PGCon 2016 will be on 17-21 May 2016 at University of Ottawa.

* 17-18 (Tue-Wed) tutorials
* 19 & 20 (Thu-Fri) talks - the main part of the conference
* 17 & 21 (Wed & Sat) The Developer Unconference & the User Unconference (both 
very popular)

PLEASE NOTE: PGCon 2016 is in May.

See http://www.pgcon.org/2016/

We are now accepting proposals for the main part of the conference (19-20 May).
Proposals can be quite simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2015 Proposal acceptance begins
19 Jan 2016 Proposal acceptance ends
19 Feb 2016 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also 

Instructions for submitting a proposal to PGCon 2016 are available
from: 



signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] PGCon 2016 call for papers

[Dan Langille]

In case you've overlooked it, you have about two weeks to submit your proposal.

PGCon 2016 will be on 17-21 May 2016 at University of Ottawa.

* 17-18 (Tue-Wed) tutorials
* 19 & 20 (Thu-Fri) talks - the main part of the conference
* 17 & 21 (Wed & Sat) The Developer Unconference & the User Unconference (both 
very popular)

PLEASE NOTE: PGCon 2016 is in May.

See http://www.pgcon.org/2016/

We are now accepting proposals for the main part of the conference (19-20 May).
Proposals can be quite simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2015 Proposal acceptance begins
19 Jan 2016 Proposal acceptance ends
19 Feb 2016 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also 

Instructions for submitting a proposal to PGCon 2016 are available
from: 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [HACKERS] could not truncate directory pg_subtrans: apparent wraparound

[Dan Langille]

If there's anything I can try on my servers to help diagnose the issues,
please let me know.  If desired, I can arrange access for debugging.

On Sat, Jun 6, 2015 at 12:51 AM, Thomas Munro thomas.mu...@enterprisedb.com
 wrote:

 On Sat, Jun 6, 2015 at 1:25 PM, Alvaro Herrera alvhe...@2ndquadrant.com
 wrote:
  Thomas Munro wrote:
 
  My idea was that if I could get oldestXact == next XID in
  TruncateSUBSTRANS, then TransactionIdToPage(oldestXact) for a value of
  oldestXact that happens to be immediately after a page boundary (so
  that xid % 2048 == 0) might give page number that is =
  latest_page_number, causing SimpleLruTruncate to print that message.
  But I can't figure out how to get next XID == oldest XID, because
  vacuumdb --freeze --all consumes xids itself, so in my first attempt
  at this, next XID is always 3 ahead of the oldest XID when a
  checkpoint is run.
 
  vacuumdb starts by querying pg_database, which eats one XID.
 
  Vacuum itself only uses one XID when vac_truncate_clog() is called.
  This is called from vac_update_datfrozenxid(), which always happen at
  the end of each user-invoked VACUUM (so three times for vacuumdb if you
  have three databases); autovacuum does it also at the end of each run.
  Maybe you can get autovacuum to quit before doing it.
 
  OTOH, if the values in the pg_database entry do not change,
  vac_truncate_clog is not called, and thus vacuum would finish without
  consuming an XID.

 I have manage to reproduce it a few times but haven't quite found the
 right synchronisation hacks to make it reliable so I'm not posting a
 repro script yet.

 I think it's a scary sounding message but very rare and entirely
 harmless (unless you really have wrapped around...).  The fix is
 probably something like: if oldest XID == next XID, then just don't
 call SimpleLruTruncate (truncation is deferred until the next
 checkpoint), or perhaps (if we can confirm this doesn't cause problems
 for dirty pages or that there can't be any dirty pages before cutoff
 page because of the preceding flush (as I suspect)) we could use
 cutoffPage = TransactionIdToPage(oldextXact - 1) if oldest == next, or
 maybe even always.

 --
 Thomas Munro
 http://www.enterprisedb.com

[HACKERS] could not truncate directory pg_subtrans: apparent wraparound

[Dan Langille]

I noticed this today on my 9.4.2 server running on FreeBSD 10.1:

Jun  5 18:59:40 slocum postgres[986]: [3957-1] LOG:  could not truncate 
directory pg_subtrans: apparent wraparound

Looking at a post from 2010, Tom Lane suggest this information was useful:

[root@slocum:/usr/local/pgsql/data/pg_subtrans] # ls -l
total 1
-rw---  1 pgsql  pgsql  8192 Jun  5 19:04 0032

This not not a high throughput server.

—
Dan Langille
http://langille.org/







signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [HACKERS] PGCon hacker lounge

[Dan Langille]

 On May 27, 2015, at 12:06 PM, Alexander Korotkov a.korot...@postgrespro.ru 
 wrote:
 
 On Wed, May 27, 2015 at 7:00 PM, Dan Langille d...@langille.org 
 mailto:d...@langille.org wrote:
 Have you been to PGCon before?  Do you remember the hacker lounge?  Do you 
 remember going there to work on stuff?  Do you recall anything about it?
 
 I remember I've tried to visit it in 2012 or 2013. That time I found empty 
 room and nobody there. Didn't try to visit it anytime after.

The reason I asked: I was trying to gauge the usefulness of the PGCon hacking 
lounge since it was first added to the schedule in 2012.

It seems it goes unused, and I was trying to see if anyone found it useful in 
the past.  At BSDCan, for example, you can find people there every night 
discussing and working.  Or perhaps just socializing.  It's a major gathering 
point.

If there is interest, we'll retain for 2015, but it seems best to remove it 
from the schedule.

—
Dan Langille
http://langille http://langille/.org/







signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] PGCon hacker lounge

[Dan Langille]

Have you been to PGCon before?  Do you remember the hacker lounge?  Do you 
remember going there to work on stuff?  Do you recall anything about it?

—
Dan Langille
http://langille.org/







signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] PGCon 2015

[Dan Langille]

In 6 weeks, people start arriving in Ottawa for PGCon 2015. Have you 
registered? There's still time. Get in today.

We have a great list of talks: http://www.pgcon.org/2015/schedule/events.en.html

Given by great speakers: http://www.pgcon.org/2015/schedule/speakers.en.html

You'll want to be there.  Don't leave it much longer.

—
Dan Langille
http://langille.org/







signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] HEADS UP: PGCon 2015 major schedule changes

[Dan Langille]

Hello,

By request, the format of PGCon 2015 will differ significantly from previous 
year.
Our goal is to give you more of what you want while still keeping the stuff 
you've always liked.

In June 2015, PGCon will be structured as follows:

Unconference: 16-17 June 2015 (Tue afternoon  all day Wed)

Beginner Tutorials: 17 June 2015 (Wed)

Talks: 18-19 June 2015 (Thu-Fri)

Advanced Tutorial: 20 June 2015 (Sat)

The big changes are:
- Unconference moved to weekdays and now 1.5 days (was one day; Saturday)
- Tutorials split between beginner and advanced, and now on Wednesday  Saturday
  (was Tuesday  Wednesday)

Why?

The unconference has become a bigger and more significant part of PGCon
for PostgreSQL contributors.  It has moved to earlier in the week to
coordinate with other developer meetings, in order to expand the
participation in development discussions and meetings around PGCon.
Additionally, the shift of some tutorials to Saturday allows tutorials to 
involve key PostgreSQL contributors without schedule conflicts.

Unfortunately, this meant moving something else to Saturday, at least for this 
year.
We considered moving the talks to earlier in the week, but we felt that our 
changes
were already disruptive and wanted to minimize the effects this late change may
have on people who have already booked travel / accommodation.  To those 
affected, we apologize and hope that this new structure will benefit everyone.

— 
Dan Langille
http://langille.org/







-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2015 - last day

[Dan Langille]

Today is your last day to submit your PGCon 2015 proposal.

-- 
Dan Langille
http://langille.org/



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2015

[Dan Langille]

Is your PGCon 2015 submission going in today or tomorrow?

-- 
Dan Langille
http://langille.org/



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2015 call for papers - reminder

[Dan Langille]

A reminder, only about a week to submit your proposal: 
http://www.pgcon.org/2015/papers.php

PGCon 2015 will be on 18-19 June 2015 at University of Ottawa.

* 16-17 (Tue-Wed) tutorials
* 18-19 (Thu-Fri) talks - the main part of the conference
* 20 (Sat) The Unconference (very popular)

PLEASE NOTE: PGCon 2015 is in June.

See http://www.pgcon.org/2015/

We are now accepting proposals for the main part of the conference (18-19 June).
Proposals can be quite simple. We do not require academic-style papers.

You have about two weeks left before submissions close.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2014 Proposal acceptance begins
19 Jan 2015 Proposal acceptance ends
19 Feb 2015 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also http://www.pgcon.org/2015/papers.php

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

—
Dan Langille
http://langille.org/



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2015 call for papers

[Dan Langille]

PGCon 2015 will be on 18-19 June 2015 at University of Ottawa.

* 16-17 (Tue-Wed) tutorials
* 18-19 (Thu-Fri) talks - the main part of the conference
* 20 (Sat) The Unconference (very popular)

PLEASE NOTE: PGCon 2015 is in June.

See http://www.pgcon.org/2015/

We are now accepting proposals for the main part of the conference (18-19 June).
Proposals can be quite simple. We do not require academic-style papers.

You have about two weeks left before submissions close.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2014 Proposal acceptance begins
19 Jan 2015 Proposal acceptance ends
19 Feb 2015 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also http://www.pgcon.org/2015/papers.php

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

—
Dan Langille
http://langille.org/



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] HEADS UP: PGCon 2015 is in June

[Dan Langille]

HEADS UP.

PGCon 2015 will be in June.  That’s a few weeks later than in previous years.

— 
Dan Langille



signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] PGCon 2014 - last chance

[Dan Langille]

Today is your last chance to submit a proposal for PGCon 2014.

PGCon 2014 will be on 20-24 May 2014 at University of Ottawa.

* 20-21 (Tue-Wed) tutorials
* 22-23 (Thu-Fri) talks - the main part of the conference
* 24 (Sat) The Unconference (very popular in 2013, the first year)

See http://www.pgcon.org/2014/


We are now accepting proposals for the main part of the conference (22-23 May).
Proposals can be quite simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2013 Proposal acceptance begins
19 Jan 2014 Proposal acceptance ends
19 Feb 2014 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also http://www.pgcon.org/2014/papers.php

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

-- 
Dan Langille - http://langille.org



signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] PGCon 2014 call for papers

[Dan Langille]

PGCon 2014 will be on 20-24 May 2014 at University of Ottawa.

* 20-21 (Tue-Wed) tutorials
* 22-23 (Thu-Fri) talks - the main part of the conference
* 24 (Sat) The Unconference (very popular in 2013, the first year)

See http://www.pgcon.org/2014/

We are now accepting proposals for the main part of the conference (22-23 May).
Proposals can be quite simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2013 Proposal acceptance begins
19 Jan 2014 Proposal acceptance ends
19 Feb 2014 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also http://www.pgcon.org/2014/papers.php

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

-- 
Dan Langille - http://langille.org



signature.asc
Description: Message signed with OpenPGP using GPGMail

[HACKERS] PGCon 2013 - CFP unconference day

[Dan Langille]

Folks,

The PGCon Call for Papers went out last month.  But you have about two weeks
left to respond.  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.

See this URL for details:

   http://lists.pgcon.org/pipermail/pgcon-announce/2012-December/90.html 

New this year, we are having an unconference on the Saturday right after the
conference. The content of the unconference will be determined, on the day,
by the attendees. We expect heavy attendance by developers and users of 
PostgreSQL.

Be sure to submit your proposal soon because time is running out.

-- 
Dan Langille - http://langille.org



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2013 - call for papers

[Dan Langille]

PGCon 2013 will be on 23-24 May 2013 at University of Ottawa.

This year, we are planning to have an un-conference day around PGCon.
This is currently being scheduled.  More information on the
un-conference will be available within a few weeks.

NOTE: the un-conference day content will be set on the day by those turning up
on that day.  We expect heavy attendance by developers and users of PostgreSQL.

We are now accepting proposals for the main part of the conference (23-24 May).
Proposals can be quite simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

1 Dec 2012 Proposal acceptance begins
19 Jan 2013 Proposal acceptance ends
19 Feb 2013 Confirmation of accepted proposals

NOTE: the call for lightning talks will go out very close to the conference.
Do not submit lightning talks proposals until then.

See also http://www.pgcon.org/2013/papers.php

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

-- 
Dan Langille - http://langille.org



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2012 Call for Papers - extension

[Dan Langille]

We apologize that http://www.bsdcan.org/ was offline for 12 hours from early 
Sunday morning.

The deadline for submissions has been extended to Tuesday 31 January.

PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 15-16 May 2012.

We are now accepting proposals for talks.  Proposals can be quite 
simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

8 Jan 2012 Proposal acceptance begins
31 Jan 2012 Proposal acceptance ends
19 Feb 2012 Confirmation of accepted proposals

See also http://www.pgcon.org/2012/papers.php

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

-- 
Dan Langille - http://langille.org


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2012 Call for Papers - reminder

[Dan Langille]

A reminder, there are three days left to get in before the deadline…

PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 15-16 May 2012.

We are now accepting proposals for talks.  Proposals can be quite 
simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

8 Jan 2012 Proposal acceptance begins
29 Jan 2012 Proposal acceptance ends
19 Feb 2012 Confirmation of accepted proposals

See also http://www.pgcon.org/2012/papers.php

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

-- 
Dan Langille - http://langille.org


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2012 Call for Papers

[Dan Langille]

PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 15-16 May 2012.

We are now accepting proposals for talks.  Proposals can be quite 
simple. We do not require academic-style papers.

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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

 8 Jan 2012 Proposal acceptance begins
29 Jan 2012 Proposal acceptance ends
19 Feb 2012 Confirmation of accepted proposals

See also http://www.pgcon.org/2012/papers.php

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

-- 
Dan Langille - http://langille.org


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2011 Call for Papers - reminder

[Dan Langille]

A reminder about PGCon 2011; the deadline is 19 January 2011.

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

We are now accepting proposals for talks.  Proposals can be quite 
simple. We do not require academic-style papers.


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 ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- PostgreSQL 9.1 and 9.2 features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

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

See also http://www.pgcon.org/2011/papers.php

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

--
Dan Langille - http://langille.org/

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2010 - registered yet?

[Dan Langille]

Registration for PGCon 2010 is open.

   http://www.pgcon.org/2010/registration.php

The full list of talks and a preliminary schedule is available here:

   http://www.pgcon.org/2010/schedule/

There are still some rooms available on campus but I recommend booking
soon as they always fill up.

-- 
Dan Langille - http://langille.org/



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] PGCon 2009 t-shirt

[Dan Langille]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tom Lane wearing the PGCon 2009 t-shirt

http://img199.imageshack.us/my.php?image=b9w.jpgvia=tfrog

- --
Dan Langille

BSDCan - The Technical BSD Conference : http://www.bsdcan.org/
PGCon  - The PostgreSQL Conference: http://www.pgcon.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoUk/8ACgkQCgsXFM/7nTxmLgCaAjTl9jI+8YdPS3LH7+9+bXQM
3FkAnRfHrmXGFwE89KLpnbq+AauxcQfk
=4Z9f
-END PGP SIGNATURE-

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] postmaster in a tight loop

[Dan Langille]

Folks,

I encountered a situation on Sunday night where the postmaster was in  
a tight
loop.  That's the conclusion we reached, but have no real proof.  I  
also have no
idea how to reproduce this situation.  This post is just an FYI in  
case it helps.


The laptop was running hot so I looked around and found pgsql to be  
the cause.

I decided to shutdown the postmaster, but it would not shutdown:

# /usr/local/etc/rc.d/postgresql stop
pg_ctl: server does not shut down

After that, I started looking closer.

For starters, here is what the system looked like:

$ date
Sun Feb 10 19:38:10 EST 2008


$ ps auwx | grep pgsql
pgsql   1172 90.0  0.4 44636  3088  ??  Rs   10:45AM  21:55.16 / 
usr/local/bin/postgres -D /usr/local/pgsql/data
pgsql   1183  0.0  0.4 44652  3392  ??  Ss   10:45AM   0:06.77  
postgres: writer process(postgres)
pgsql   1184  0.0  0.4 44652  3176  ??  Ss   10:45AM   0:04.42  
postgres: wal writer process(postgres)
pgsql   1185  0.0  0.4 44884  3336  ??  Ss   10:45AM   0:03.35  
postgres: autovacuum launcher process(postgres)
pgsql   1186  0.0  0.4  8588  3060  ??  Ss   10:45AM   0:03.77  
postgres: stats collector process(postgres)


A little bit from top:

last pid: 89359;  load averages:  3.10,  2.84,   
2.30   
up 0+08:53:20  19:37:54

84 processes:  5 running, 79 sleeping
CPU states: 48.3% user,  0.8% nice, 50.8% system,  0.0% interrupt,   
0.0% idle

Mem: 306M Active, 235M Inact, 104M Wired, 27M Cache, 85M Buf, 68M Free
Swap: 512M Total, 512M Free

  PID USERNAMETHR PRI NICE   SIZERES STATETIME   WCPU  
COMMAND
 1172 pgsql 1 1300 44636K  3088K RUN 22:18 77.34%  
postgres

 1387 root  1 1000 85936K 62032K RUN 10:48  4.49% Xorg
89357 dan   1   80  1860K  1424K wait 0:00  1.00% sh
46507 dan   1  960 15636K  9900K select   1:52  0.05%  
npviewer.bin
88563 dan   1  960 28856K 21128K RUN  0:01  0.05%  
kdeinit


$ uname -a
FreeBSD laptop.unixathome.org 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE  
#2: Wed Nov  7 10:54:48 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ 
PCBSD  i386


Running PostgreSQL 8.3.0

Looking at ktrace output, I saw a lot of this:

1172 postgres CALL  kse_release(0xbfbfd500)
1172 postgres RET   kse_release -1 errno 22 Invalid argument

The ldd output for postgres is:

[EMAIL PROTECTED]:/usr/home/dan] $ ldd /usr/local/bin/postgres
/usr/local/bin/postgres:
libintl.so.8 = /usr/local/lib/libintl.so.8 (0x2835a000)
libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x28363000)
libssl.so.4 = /usr/lib/libssl.so.4 (0x2846f000)
libcrypto.so.4 = /lib/libcrypto.so.4 (0x2849d000)
libcrypt.so.3 = /lib/libcrypt.so.3 (0x2859)
libm.so.4 = /lib/libm.so.4 (0x285a8000)
libpthread.so.2 = /lib/libpthread.so.2 (0x285be000)
libc.so.6 = /lib/libc.so.6 (0x285e3000)
libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x286c9000)
libz.so.3 = /lib/libz.so.3 (0x287b6000)
[EMAIL PROTECTED]:/usr/home/dan] $

The server was compiled with these options:

[EMAIL PROTECTED]:~] $ less /var/db/ports/postgresql83/options
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
# Options for postgresql-client-8.3.0
_OPTIONS_READ=postgresql-client-8.3.0
WITH_NLS=true
WITHOUT_PAM=true
WITHOUT_LDAP=true
WITHOUT_MIT_KRB5=true
WITHOUT_HEIMDAL_KRB5=true
WITHOUT_OPTIMIZED_CFLAGS=true
WITH_XML=true
WITH_TZDATA=true
WITHOUT_DEBUG=true
WITHOUT_INTDATE=true
[EMAIL PROTECTED]:~] $



--
Dan Langille -- http://www.langille.org/
[EMAIL PROTECTED]





---(end of broadcast)---
TIP 6: explain analyze is your friend

[HACKERS] PGCon 2008 - call for papers

[Dan Langille]

Hello folks,

PGCon 2008 will be held 22-23 May 2008, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 20-21 May 2008.

We are now requesting proposals for presentations.

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 few 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

Both users and developers are encouraged to share their experiences.

The schedule is:

 19 Dec 2007 Proposal acceptance begins
 19 Jan 2008 Proposal acceptance ends
 19 Feb 2008 Confirmation of accepted proposals
 19 Apr 2008 Final papers/slides must arrive no later than this date

See also http://www.pgcon.org/2008/papers.php

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

--
Dan Langille - http://www.langille.org/
BSDCan - The Technical BSD Conference: http://www.bsdcan.org/
PGCon  - The PostgreSQL Confernce: http://www.pgcon.org/


---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq

Re: [HACKERS] PGCon 2007 Program Committee

[Dan Langille]

On 6 Jan 2007 at 12:09, Oleg Bartunov wrote:

 What's about spronsoring ?

Are you asking if your and Teodor can be sponsored?

 I and Teodor would like to present new full text search, now built into
 PostgreSQL core. We already have patch for 8.3 and current
 documentation is available
 http://mira.sai.msu.su/~megera/pgsql/ftsdoc/ 

Please submit a proposal at the URL below.  :)

 
 Oleg
 On Fri, 5 Jan 2007, Dan Langille wrote:
 
  I have the pleasure of announcing your PGCon 2007 program committee.
 
  Bruce Momjian
  Christopher Browne
  Josh Berkus
  Robert Treat
  Luke Lonergan
  Neil Conway
  Robert Bernier
 
  These people are responsible for reviewing your submissions and
  selecting the presentations for PGCon 2007.
 
  Speaking of presentations, now that the major holidays are over,
  please submit your proposal now.  Instructions for submissions are at
  http://www.pgcon.org/2007/submissions.php
 
  The original call for papers: http://www.pgcon.org/2007/papers.php
 
  NOTE: Please get your proposal in by 19 Jan (that is in two weeks).
 
 
 
   Regards,
   Oleg
 _
 Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
 Sternberg Astronomical Institute, Moscow University, Russia
 Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
 phone: +007(495)939-16-83, +007(495)939-23-83
 
 ---(end of broadcast)---
 TIP 3: Have you checked our extensive FAQ?
 
http://www.postgresql.org/docs/faq
 



-- 
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
PGCon - The PostgreSQL Conference - http://www.pgcon.org/



---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly

Re: [HACKERS] [pgsql-advocacy] PGCon 2007 Program Committee

[Dan Langille]

On 7 Jan 2007 at 1:39, Oleg Bartunov wrote:

 On Sat, 6 Jan 2007, Dan Langille wrote:
 
  On 6 Jan 2007 at 12:09, Oleg Bartunov wrote:
 
  What's about spronsoring ?
 
  Are you asking if your and Teodor can be sponsored?
 
 yes
 
 
  I and Teodor would like to present new full text search, now built into
  PostgreSQL core. We already have patch for 8.3 and current
  documentation is available
  http://mira.sai.msu.su/~megera/pgsql/ftsdoc/
 
  Please submit a proposal at the URL below.  :)
 
 ok, I'll try, but first I need to know about support. It's too expensive
 for us.

Please submit your proposal.  If it is accepted, we'll find a way to 
get you there.

-- 
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
PGCon - The PostgreSQL Conference - http://www.pgcon.org/



---(end of broadcast)---
TIP 6: explain analyze is your friend

[HACKERS] PGCon 2007 Program Committee

[Dan Langille]

I have the pleasure of announcing your PGCon 2007 program committee. 

Bruce Momjian
Christopher Browne
Josh Berkus
Robert Treat
Luke Lonergan
Neil Conway
Robert Bernier

These people are responsible for reviewing your submissions and 
selecting the presentations for PGCon 2007.

Speaking of presentations, now that the major holidays are over, 
please submit your proposal now.  Instructions for submissions are at 
http://www.pgcon.org/2007/submissions.php

The original call for papers: http://www.pgcon.org/2007/papers.php

NOTE: Please get your proposal in by 19 Jan (that is in two weeks).

-- 
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
PGCon - The PostgreSQL Conference - http://www.pgcon.org/



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq

[HACKERS] Undefined symbol elog

[Dan Langille]

Hi folks,

I upgraded two servers from 7.3.* to 7.4.1.  In both cases, the 
pgcrypto functions failed to migrate..  I used pg_dumpall.  This is 
the cause of the problem:  

freshports=# CREATE FUNCTION digest (text, text) RETURNS bytea
freshports-# AS '$libdir/pgcrypto', 'pg_digest'
freshports-# LANGUAGE c;
ERROR:  could not load library 
/usr/local/lib/postgresql/pgcrypto.so: dlopen 
'/usr/local/lib/postgresql/pgcrypto.so' failed. 
(/usr/local/lib/postgresql/pgcrypto.so: 
Undefined symbol elog)

Recompiling and installing contrib/pgcrypto made the problem go away. 
I found no mention of this problem in the archives.  

FWIW: I was using the FreeBSD port on 4.9-STABLE.

-- 
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

[HACKERS] Undefined symbol elog

[Dan Langille]

My search was wrong.  This is a known issue.

Sorry for the post.
-- 
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly

Re: [HACKERS] dump + restore didn't include schemas

[Dan Langille]

On 30 Jan 2004 at 23:34, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  I upgraded two servers today from 7.3.* to 7.4.1.  In both cases, the 
  schemas which existed in the original databases were not created in 
  the new database.
  New issue?  Known bug?
 
 New one on me.  Look at the log output from when the dump was being
 restored.  I suppose there must be an error message from the CREATE
 SCHEMA commands --- what is it?

I found three of these messages in /var/log/messages on the box which 
had the problem.

ERROR:  permission denied for database pg_freebsddiary.org.schemas

Nothing else.  I don't have the output from the restore.  I tried 
reproducing the problem on another box but schemas were always 
correctly created.  I can't reproduce the problem situation.  Sorry.
-- 
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/


---(end of broadcast)---
TIP 8: explain analyze is your friend

Re: [HACKERS] dump + restore didn't include schemas

[Dan Langille]

On 31 Jan 2004 at 11:56, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  I upgraded two servers today from 7.3.* to 7.4.1.  In both cases, the 
  schemas which existed in the original databases were not created in 
  the new database.
 
  I found three of these messages in /var/log/messages on the box which 
  had the problem.
 
  ERROR:  permission denied for database pg_freebsddiary.org.schemas
 
 Oh, I bet I know what this is: the owners of those schemas don't have
 CREATE SCHEMA privileges, right?  You made the schemas as superuser with
 CREATE SCHEMA foo AUTHORIZATION bar.
 
 7.4's pg_dump will use AUTHORIZATION so that situations like this
 restore correctly, but 7.3's pg_dump is stupid and tries to create the
 schema as its owner.

Does it matter that I used pg_dumpall?

 In general I recommend that during an upgrade, you use the new version's
 pg_dump to dump from the old server.  This way you get the benefit of
 whatever improvements have been made in pg_dump since the previous
 release.

Should that recommendation be added to the If You Are Upgrading 
section of INSTALL?
-- 
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/


---(end of broadcast)---
TIP 8: explain analyze is your friend

Re: [HACKERS] [GENERAL] Are we backwards on the sign of timezones?

[Dan Langille]

On 4 Jul 2003 at 23:22, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  Now that my NZ server is up and running:
  template1=# select now();
   2003-07-05 12:47:15.444535+12
 
  That doesn't look backwards to me.
 
 Try EXTRACT(timezone_hour from now());
 
 The timestamp I/O routines are using what I think is the correct sign.
 EXTRACT() is at variance.  So is SET TIMEZONE with a numeric offset.

select now(), extract(timezone_hour from now());
  now  | date_part
---+---
 2003-07-05 23:15:09.760771+12 |   -12

Yep, I'd say that should return +12, not -12.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

Re: [HACKERS] [GENERAL] Are we backwards on the sign of timezones?

[Dan Langille]

On 3 Jul 2003 at 13:18, Tom Lane wrote:

 Comments?

The message headers for this email contained:

Received: from www.postgresql.com (www.postgresql.com 
[64.117.225.209])
by m20.unixathome.org (Postfix) with ESMTP id 77EC27A69
for [EMAIL PROTECTED]; Thu,  3 Jul 2003 15:33:13 -0400 (EDT)


My mail server is m20.unixathome.org and yes, it's four hours behind 
GMT.  My PG server in Vancouver, shows this:

# select current_time;
   timetz

 12:36:43.579071-07

Which is three hours west of here (Ottawa).I was going to check 
my NZ server, but it's in the process of upgrading PG..


-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] [GENERAL] Are we backwards on the sign of timezones?

[Dan Langille]

On 3 Jul 2003 at 13:18, Tom Lane wrote:

 Comments?

Now that my NZ server is up and running:

template1=# select now();
  now
---
 2003-07-05 12:47:15.444535+12

That doesn't look backwards to me.  Perhaps I don't understand the 
problem.  After rereading your original post:

 Local time is equal to UTC (Coordinated Universal Time) plus
 the time zone displacement,

In the above, the local time is  2003-07-05 12:47:15.444535.  UTC 
would be  2003-07-05 00:47:15.444535.  To which we add +12 hours to 
get local time.  That appears to be consistent with the SQL99 spec.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] What goes into the security doc?

[Dan Langille]

On 22 Jan 2003 at 13:29, Christopher Kings-Lynne wrote:

 Recommend always running initdb -W and setting all pg_hba entries to md5.

Thanks.  I also encountered this item on IRC:

[09:26] fede2 Guys, is there a problem with using /bin/true of 
/bin/false as the shell of the postgres user? The docs only says 
adduser postgres , witch will give postgres a nice shell.
[09:27] fede2 I'm asking because the guys from Gentoo (thats a 
distro FWIW), want to use either /bin/false of /bin/true as postgres' 
shell.
[09:27] dvl fede2: it means you won't be able to become the 
postgres user to run commands.
[09:27] mmc_ ... to run SHELL commands.
[09:29] fede2 dvl: Aldo it's not the same, one could use su -c foo 
postgres to workarround it.
[09:30] fede2 dvl: I was wondering if it had an even heavier 
reason, besides that.
[09:34] mmc_ fede2: tha manpage of su says, that -c args is treated 
by the login shell !
[09:35] fede2 mmc_: Hmm.. true. That makes it a heavy enough 
reason. Thanks.
[09:35] * fede2 departs
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[HACKERS] What goes into the security doc?

[Dan Langille]

With reference to my post to the PostgreSQL Password Cracker on
2003-01-02, I've promised to write a security document for the project.
Here it is, Sunday night, and I can't sleep.  What better way to get there
than start this task...

My plan is to write this in very simple HTML.  I will post the draft
document on my website and post the URL here from time to time for
feedback. Please make suggestions for content.  So far, I will cover these
items:

- .pgpass (see
http://developer.postgresql.org/docs/postgres/libpq-files.html)
- local connections
- remote connections (recommending SSL)
- pg_hba (only in passing, most of that is at
http://www.postgresql.org/idocs/index.php?client-authentication.html)
- running the postmaster as a specific user

That doesn't sound like much.  Surely you can think of something else to
add.  Should I post this to another list for their views?

OK, that's done it.  I'm ready for sleep now.


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] PostgreSQL site, put up or shut up?

[Dan Langille]

On 13 Jan 2003 at 9:45, Vince Vielhaber wrote:

 On Mon, 13 Jan 2003 [EMAIL PROTECTED] wrote:
 
   FTP is just over 800MB, plan for growth.
   WEB is just over 90MB, can't tell you what to plan for there.
 
  Sorry to be dense, but what time period is this for?
 
 Any given day.  It's disk space, not traffic.

I think anyone thinking of putting up a mirror will want to know 
traffic volumes.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] psql and readline

[Dan Langille]

On 9 Jan 2003 at 9:15, Robert Treat wrote:

 On Thu, 2003-01-09 at 08:45, Peter Mount wrote:
  On Wed, 8 Jan 2003, Dan Langille wrote:
   On 8 Jan 2003 at 12:28, Bruce Momjian wrote:
Tom Lane wrote:
 Alexander M. Pravking [EMAIL PROTECTED] writes:
  On Wed, Jan 08, 2003 at 10:53:51AM +0100, Ian Barwick wrote:
  On Wednesday 08 January 2003 07:55, Christopher Kings-Lynne
  wrote:
  Is there any way of making the 'up' arrow retrieve all of
  the last multiline query, instead of just the last line? 
  It's really annoying working with large multiline queries
  at the moment...
  
  Not that I know of, but you can use \e to edit the query in
  your favourite editor.
 
  Sure. But \e puts \e into history, instead of the query
  itself :(
 
 Hm, so it does.  It seems like the edited query should go into
 history, at least when you execute it.  Peter, is this
 fixable?

Wow, that would be a nifty trick, though they really did type \e
and not the query the pulled in from the editor.
   
   What about those of us who want to use \e repeatedly?  Will that
   be in the history buffer?
  
  The number of times I've cursed things over the years, I would have
  thought having the edited query in the history would be more useful
  than \e - the latter is only three key presses any how ;-)
  
 
 Or if the query could be appended after the \e, it would only be a
 quick double-up to get back to the \e.

As this is changing existing behaviour, I think adding an optional  
switch to revert to the old behaviour is a good idea.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] psql and readline

[Dan Langille]

resent with my real mail address...

On 9 Jan 2003 at 13:45, Peter Mount wrote:

 On Wed, 8 Jan 2003, Dan Langille wrote:
 
  On 8 Jan 2003 at 12:28, Bruce Momjian wrote:
  
   Tom Lane wrote:
Alexander M. Pravking [EMAIL PROTECTED] writes:
 On Wed, Jan 08, 2003 at 10:53:51AM +0100, Ian Barwick wrote:
 On Wednesday 08 January 2003 07:55, Christopher Kings-Lynne
 wrote:
 Is there any way of making the 'up' arrow retrieve all of the
 last multiline query, instead of just the last line?  It's really
 annoying working with large multiline queries at the moment...
 
 Not that I know of, but you can use \e to edit the query in your
 favourite editor.

 Sure. But \e puts \e into history, instead of the query itself :(

Hm, so it does.  It seems like the edited query should go into
history, at least when you execute it.  Peter, is this fixable?
   
   Wow, that would be a nifty trick, though they really did type \e and
   not the query the pulled in from the editor.
  
  What about those of us who want to use \e repeatedly?  Will that be in
  the history buffer?
 
 The number of times I've cursed things over the years, I would have 
 thought having the edited query in the history would be more useful than \e
 - the latter is only three key presses any how ;-)

It is easier to edit things within an editor than within the command line, 
especially if using very long complex statements involving 8 or 9 tables 
and nested/outer JOINS.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] psql and readline

[Dan Langille]

On 9 Jan 2003 at 10:13, Bruce Momjian wrote:

 Justin Clift wrote:
  Bruce Momjian wrote:
  snip
   Let's suppose I am writing a query, and then I do \e to edit the
   query, and I exit the editor and return to psql.  Suppose I decide
   I want to reedit, so I up arrow.  I would expect to get \e, not
   the query I just edited, no?
  
  Wouldn't it depend on how this gets implemented?
  
  Maybe least negative impact approach (suggested already): If the
  large command that was edited is put in the command history before
  the \e, then both are available and there is no big change from
  expected behaviour.
  
  i.e. one up arrow get the previous \e, and a second up arrow would
  bring up the command that was worked upon.
 
 Makese sense.  However, it still has the shock factor of displaying a
 huge query, which is usually what is involved when using the editor. 

Which is a good indicator that a way to turn it off is a good idea.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] psql and readline

[Dan Langille]

On 8 Jan 2003 at 12:28, Bruce Momjian wrote:

 Tom Lane wrote:
  Alexander M. Pravking [EMAIL PROTECTED] writes:
   On Wed, Jan 08, 2003 at 10:53:51AM +0100, Ian Barwick wrote:
   On Wednesday 08 January 2003 07:55, Christopher Kings-Lynne
   wrote:
   Is there any way of making the 'up' arrow retrieve all of the
   last multiline query, instead of just the last line?  It's
   really annoying working with large multiline queries at the
   moment...
   
   Not that I know of, but you can use \e to edit the query in your
   favourite editor.
  
   Sure. But \e puts \e into history, instead of the query itself
   :(
  
  Hm, so it does.  It seems like the edited query should go into
  history, at least when you execute it.  Peter, is this fixable?
 
 Wow, that would be a nifty trick, though they really did type \e and
 not the query the pulled in from the editor.

What about those of us who want to use \e repeatedly?  Will that be 
in the history buffer?
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] Have people taken a look at pgdiff yet?

[Dan Langille]

On Tue, 7 Jan 2003, Justin Clift wrote:

 Hi everyone,

 Just found out that the pgdiff utility (the one for comparing two
 different PostgreSQL database's) was released and uploaded to
 SourceForge in November:

 http://sourceforge.net/projects/pgdiff

 Have people already looked at this?

I started... but had to install and configure AOLServer, which took more
time than I had allotted to thie experiment.  I never was able to get a
diff to run.  I think a good pratical and working example is needed for
that utility.  I'd like to see how it works.


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] New Portal in Place, DNS switched ...

[Dan Langille]

On 7 Jan 2003 at 16:25, mlw wrote:

 I think banner ads that build on PostgreSQL's message is a good thing.
 A RedHat ad, maybe IBM, etc. Companies with a related purpose to the
 PostgreSQL mission will offset some of the cost and help build the
 cedibility of the site.
 
 Hotel ads and sweepstakes are a bad idea, though.

I think that those who are objecting to ads on the site should follow 
the suggestion given by Josh Berkus at 
http://archives.postgresql.org/pgsql-general/2003-01/msg00191.php

In other words, stop providing suggestions as to what can be done.  
Get off your own ass and do it.  In short, put up or shut up.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] New Portal in Place, DNS switched ...

[Dan Langille]

On 6 Jan 2003 at 18:44, [EMAIL PROTECTED] wrote:

 If the banner ads (as previously stated) do not bring in much revenue,
 is there a reason to keep them?

This has been mentioned more than once AFAIK. It is in payment to 
those who have provided mirror services.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] OS/400 support?

[Dan Langille]

On Mon, 6 Jan 2003, Tom Lane wrote:

 Justin Clift [EMAIL PROTECTED] writes:
  Info:
  http://search400.techtarget.com/sDefinition/0,,sid3_gci331973,00.html

 That page quoth

 OS/400 and its related software has added support for:

  The Portable Application Solutions Environment (PASE), which
  supports a subset of the AIX environment so that Unix applications can
  be ported and run on the AS/400

 This suggests that our AIX port might work with little or no tweaking.
 Or perhaps not; subset could cover a multitude of sins.  But it'd be
 worth trying.

That would be very wild if we could do that.  Who volunteered? ;)


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [GENERAL] [HACKERS] v7.3.1 Bundled and Released ...

[Dan Langille]

On Sat, 4 Jan 2003, Tom Lane wrote:

 Marc G. Fournier [EMAIL PROTECTED] writes:
  I never considered tag'ng for minor releases as having any importance,
  since the tarball's themselves provide the 'tag' ... branches give us the
  ability to back-patch, but tag's don't provide us anything ... do they?

 Well, a tag makes it feasible for someone else to recreate the tarball,
 given access to the CVS server.  Dunno how important that is in the real
 world --- but I have seen requests before for us to tag release points.

FWIW, in the real world, a release doesn't happen if it's not taqged.


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] New Portal in Place, DNS switched ...

[Dan Langille]

On 5 Jan 2003, Neil Conway wrote:

 Obviously, but it's VERY unprofessional for us to show ads to users on
 our website. It goes without saying, but pretty much every other
 non-trivial OSS project doesn't have ads on their main website.
 Displaying ads makes us look more like a Geocities site than a
 legitimate competitor to Oracle/DB2/etc.

I have no problem with the ads.  I disagree with the viewpoints above.


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [GENERAL] [HACKERS] v7.3.1 Bundled and Released ...

[Dan Langille]

On Sat, 4 Jan 2003, Peter Eisentraut wrote:

 Greg Copeland writes:

  Just a reminder, there still doesn't appear to be a 7.3.1 tag.

 There is a long tradition of systematically failing to tag releases in
 this project.  Don't expect it to improve.

It was I who suggested that a release team would be a good idea.  I think
that was soundly rejected.  I still think it's a good idea.  If only to
ensure that things are properly tagged, the right annoucements go out at
the right times, that a code freeze goes into effect, etc. These concepts
are not new.  A release is an important step in the life cycle.

I volunteered to document the release procedure as it resides only within
lore and a couple of heads.  I have yet to start.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [GENERAL] [HACKERS] v7.3.1 Bundled and Released ...

[Dan Langille]

msg resent because I incorrectly copied/pasted some addresses.  
Sorry.

On 4 Jan 2003 at 11:08, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  On Sat, 4 Jan 2003, Peter Eisentraut wrote:
  There is a long tradition of systematically failing to tag releases
  in this project.  Don't expect it to improve.
 
  It was I who suggested that a release team would be a good idea.
 
 We *have* a release team.

I have a suggestion.  Let us document who is the release team and who 
is responsible for each step of the release.  Perhaps that is the 
problem: a lack of process.

I'll add that to my list of things I've promised to do.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [GENERAL] [HACKERS] v7.3.1 Bundled and Released ...

[Dan Langille]

msg resent because I incorrectly copied/pasted some addresses.  Sorry.

On 4 Jan 2003 at 11:08, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  On Sat, 4 Jan 2003, Peter Eisentraut wrote:
  There is a long tradition of systematically failing to tag releases
  in this project.  Don't expect it to improve.
 
  It was I who suggested that a release team would be a good idea.
 
 We *have* a release team.  Your problem is that Marc, who is the man
 who would need to do this, doesn't appear to consider it an important
 thing to do.  Try to convince him to put it on his checklist.

Marc?  Is this true?  You don't consider it important to tag the 
release?  I'm quite sure that's not the case and that Marc does 
consider it important.  It's just something which he forgot to do.

A recent post by Greg Copeland implies this item is on his checklist.

IMHO, it is vital that the tree is properly tagged for each release.  
AFAIK, a tag can be laid with with respect to timestamp value.  So 
why don't we just do it?
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] Upgrading rant.

[Dan Langille]

On Fri, 3 Jan 2003, Bruce Momjian wrote:

 Is pg_upgrade too hard to run?  Is no one really interested in it?

All of my boxes are still on 7.2.3.  Does that represent a viable test
base?


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] PostgreSQL Password Cracker

[Dan Langille]

I'll do that.  Justin: What's the URL for the .pgpass stuff?  So far I see
mention of using SSL.  That's two items to cover.  Anything else?

On Wed, 1 Jan 2003, Bruce Momjian wrote:


 Yes, I have been feeling we should do that.  Justin pointed out just
 yesterday that .pgpass is only mentioned in libpq documentation, and in
 fact there is lots of stuff mentioned in libpq that releates to the
 other interfaces, so it should be pulled out and put in one place.

 Does anyone want to tackle this?

 ---

 Tom Lane wrote:
  Bruce Momjian [EMAIL PROTECTED] writes:
   What do others think?  I am not sure myself.
 
  There should definitely be someplace that recommends using SSL across
  insecure networks (if there's not already).  But it doesn't seem to me
  to qualify as a FAQ entry.  Somewhere in the admin guide seems more
  appropriate.  Perhaps under Client Authentication?
 
  Maybe someone could even put together enough material to create a whole
  chapter on security considerations --- this is hardly the only item
  worthy of mention.
 
  regards, tom lane
 

 --
   Bruce Momjian|  http://candle.pha.pa.us
   [EMAIL PROTECTED]   |  (610) 359-1001
   +  If your life is a hard drive, |  13 Roberts Road
   +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

 ---(end of broadcast)---
 TIP 5: Have you checked our extensive FAQ?

 http://www.postgresql.org/users-lounge/docs/faq.html



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[HACKERS] new project - PostgresSQL based voting script

[Dan Langille]

See http://polls.unixathome.org/

Goal: create a voting script which uses PostgreSQL to store the data.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] [GENERAL] Cast your vote ...

[Dan Langille]

On 2 Jan 2003 at 7:53, Charles H. Woloszynski wrote:

 Yeah, the registration was painless and enough options to disable it
 annoying you. Count my vote cast for PostgreSQL.  I encourage everyone
 else to do the same.  In the big picture, marketing statements like
 this survey mean alot more than most technical folks want to
 acknowledge.  
 
 Please vote for your favorite database.

Coincidentally, I've just started up a voting script project... see 
http://polls.unixathome.org/
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] [GENERAL] Cast your vote ...

[Dan Langille]

On 2 Jan 2003 at 21:30, Jeroen T. Vermeulen wrote:

  Coincidentally, I've just started up a voting script project... see
  http://polls.unixathome.org/
 
 Does it support hanging chads?

Now is the time to decide that
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] why was libpq.so's version number bumped?

[Dan Langille]

On Mon, 30 Dec 2002, Palle Girgensohn wrote:

 One of the reasons I ask is, if it is a good reason, like say security,
 maybe I can persuade the FreeBSD port responsible guys to bring the port
 into the upcoming FreeBSD 5.0 release. The port freeze was introduced just
 before pg-7.3 was released, so nothing new will be admitted unless it is a
 security fix, more or less, which means FreeBSD 5.0 will probably ship with
 7.2.3, which would be a disappointment...

If anything, the ports tree on the CD will contain a reference to 7.2.3.
PostgreSQL itself is not shipped.  The ports tree can be cvsup'd to the
latest, when the cvs repository is updated.  At present there is a ports
freeze.  This is the normal situation just prior to a major release.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] why was libpq.so's version number bumped?

[Dan Langille]

On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:

 Since going from 7.2 to 7.3 is a significant upgrade, the FreeBSD guys would
 probablyu be right tho to refuse such a major upgrade...  Still, it's a pity
 though.  Postgres 7.3 has been tested and works fine on FreeBSD 5.

FreeBSD uses something called a ports tree.  This is quite separate from
the source tree, which is used to create FreeBSD 5.  The issue is not
whether or not 7.3 has been tested and works.  When you have nearly
8000 ports, it makes sense to freeze them just prior to a release.  Code
freezes are standard practice.  I which more projects used them.

 ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
 Actually, maybe it was a good thing since if 7.3.1 becomes the new standard
 port people won't be bitten so much by the library version bump.

My guess: because of the port freeze now in effect.


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] why was libpq.so's version number bumped?

[Dan Langille]

On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:

 ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??

I forgot one other possible answer: perhaps the port maintainer is taking
a well deserved holiday?


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] why was libpq.so's version number bumped?

[Dan Langille]

On Mon, 30 Dec 2002, Palle Girgensohn wrote:

 --On måndag, december 30, 2002 06.35.22 -0500 Dan Langille
 [EMAIL PROTECTED] wrote:

  On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
 
  ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
 
  I forgot one other possible answer: perhaps the port maintainer is taking
  a well deserved holiday?

 :)  Well, not really, it is because of the port freeze. I don't maintain
 the -devel port, Sean Chittenden does. It seems logical that he maintains
 it, since he has commit rights to the ports tree. It was used during
 postgresql's beta phase, and it will be removed after the port freeze, only
 to resurrect at the next beta phase. This is the plan, anyway. :)

I liked and used the -devel port.  I think the concept should be retained.

  Since going from 7.2 to 7.3 is a significant upgrade, the FreeBSD guys
  would probablyu be right tho to refuse such a major upgrade...  Still,
  it's a pity though.  Postgres 7.3 has been tested and works fine on
  FreeBSD 5.

 True, perhaps, but if the old version has security flaws... Also, since 5.0
 is a new major version for FreeBSD, most binaries need relinking to fully
 utilize the new system - wouldn't it be clever to have the new postgres
 libpq relinked at the same time as well...?

What about the other 8000 or so ports?  Should we halt FreeBSD development
so they all have the latest version as well?  I think not. At some point,
a line must be drawn.

 --On måndag, december 30, 2002 06.24.38 -0500 Dan Langille
 [EMAIL PROTECTED] wrote:
 
  If anything, the ports tree on the CD will contain a reference to 7.2.3.
  PostgreSQL itself is not shipped.  The ports tree can be cvsup'd to the
  latest, when the cvs repository is updated.  At present there is a ports
  freeze.  This is the normal situation just prior to a major release.

 Well, on the DVD or four-disk-set, there will be a package of 7.2.3, so in
 a way, postgreSQL is actually shipped...

Given that there are almost 8000 ports, it is simply not practical to hold
everything up while we get the latest of everything.  Exceptions are
allowed, but again, I don't have a problem with it.

 Well, we'll see. 7.3 has been in gnats for some time now. I'll send in the
 new 7.3.1 and send a few emails lobbying for it, and let the guys
 responsible decide if it a pre- or post-5.0 port...

I don't see it as a big deal.  It's just a ports tree entry going out with
5.  That entry can be cvsup'd and updated to the latest and greatest.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] PostgreSQL article

[Dan Langille]

On 27 Dec 2002 at 8:37, Bruce Momjian wrote:

 Here's another nice article about PostgreSQL in the enterprise:
 
  http://linuxworld.com.au/news.php3?nid=2095tid=1

Those on the advocacy list saw this posted a few days ago:

http://archives.postgresql.org/pgsql-advocacy/2002-12/msg00203.php
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

[HACKERS] http://www.postgresql.org/idocs/ is down

[Dan Langille]

http://www.postgresql.org/idocs/ is down

Warning: Unable to connect to PostgreSQL server: The Data Base System 
is shutting down in /usr/local/www/www/idocs/opendb.php on line 3
Unable to access database
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] Let's create a release team

[Dan Langille]

On 10 Dec 2002 at 0:56, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  Is the process documented?  Any set procedure?  Who knows how to do
  it?
 
 Er ... nope, nope, the core bunch ...

Sounds like we need to do a brain dump then.  I just happen to have 
some equipment left over from The Matrix

  If these things are not documented, they should be.
 
 Most of the undocumented details of the release process are in the
 heads of Marc Fournier and Bruce Momjian.  If either of them falls off
 the end of the earth, we have worse troubles than whether we remember
 how to do a release

On a project, anyone is replaceable.  And anyone might leave for any 
number of reasons.  If they do, the affect upon the project will be 
minimized by having the major processes documented.

 --- for example: Marc owns, runs, and pays for the
 postgresql.org servers.

Is the cvs repo mirrored?

 (Me, I just hack code, so I'm replaceable.)

Yeah, yeah, stop being humble... ;)

 But if you want to try to document the process better, there are some
 details written down already (eg, src/tools/RELEASE_CHANGES) and I'm
 sure Marc and Bruce would cooperate in writing down more.

That's a good start. It looks like a list of things easily forgotten 
but if forgotten, make us look bad.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] Let's create a release team

[Dan Langille]

On 10 Dec 2002 at 9:34, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  --- for example: Marc owns, runs, and pays for the
  postgresql.org servers.
 
  Is the cvs repo mirrored?
 
 Anyone running cvsup would have a complete copy of the source CVS, I
 believe.  It would be more troubling to reconstruct the mailing list
 archives; I'm not sure that those are mirrored anywhere

Do you mean the repository, or the source.  The repository is the ,v 
files  The source isn't.  Most developers would have the source, 
but not necessarily the repo.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] Let's create a release team

[Dan Langille]

On 9 Dec 2002 at 11:38, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  Let's create a release team.  This strategy is one well established
  in other projects and in industry.  For lack of a better starting
  reference, let me suggest http://www.freebsd.org/releng/charter.html
  as a starting point for consideration.  See also
  http://www.freebsd.org/releng/index.html.  
 
  This will also lighten the load on the core team allowing them to
  focus on development and such.  
 
 I don't really see any value-added here.  The core committee's only
 routinely-exercised function is to organize releases; separating that
 out would leave core with nothing to do.  

So we already have a release team, but not titled as such.

 Also, to the extent that
 core has any real or perceived authority in the project, I think it
 comes from having control of the release process --- there's surely no
 other reason for people to defer to the core team as a group (as
 opposed to whatever respect might be accorded to individual people as
 a result of their individual contributions).

Is the process documented?  Any set procedure?  Who knows how to do 
it?

 So ISTM such a
 reorganization would leave the core committee as a figurehead and make
 the release team into the effective new core.

Is 'core' the same as 'steering'?  I couldn't find any reference to 
core committe or core team via google.  At 
http://developer.postgresql.org/bios.php I see the group of people 
referred to as Steering.  Is their function defined anywhere?

If these things are not documented, they should be.  Where do I 
start?
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[HACKERS] Let's create a release team

[Dan Langille]

Hi folks,

Let's create a release team.  This strategy is one well established 
in other projects and in industry.  For lack of a better starting 
reference, let me suggest http://www.freebsd.org/releng/charter.html 
as a starting point for consideration.  See also 
http://www.freebsd.org/releng/index.html.  

This will also lighten the load on the core team allowing them to 
focus on development and such.  

cheers



-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

[HACKERS] 7.4 - TODO : IpcSemaphoreCreate: No space left on device

[Dan Langille]

This error is accompanied by a suggestion to change SEMMNI or SEMMNS. 
 In this case, that suggestion is not appropriate.  Read below for 
the scenario.

Suggestion: Can we modify the error message to include checking for a 
running postmaster?

Reasoning:

During my dbinit, I found the following error message.

# su -l pgsql -c initdb
The files belonging to this database system will be owned by user 
pgsql.
This user must also own the server process.

The database cluster will be initialized with locale C.

creating directory /usr/local/pgsql/data... ok
creating directory /usr/local/pgsql/data/base... ok
creating directory /usr/local/pgsql/data/global... ok
creating directory /usr/local/pgsql/data/pg_xlog... ok
creating directory /usr/local/pgsql/data/pg_clog... ok
creating template1 database in /usr/local/pgsql/data/base/1... 
IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: No space 
left on device

This error does *not* mean that you have run out of disk space.

It occurs when either the system limit for the maximum number of
semaphore sets (SEMMNI), or the system wide maximum number of
semaphores (SEMMNS), would be exceeded.  You need to raise the
respective kernel parameter.  Alternatively, reduce PostgreSQL's
consumption of semaphores by reducing its max_connections parameter
(currently 1).

The PostgreSQL Administrator's Guide contains more information about
configuring your system for PostgreSQL.


initdb failed.
Removing /usr/local/pgsql/data.

###

Here's what happened:

I removed the old installs of pg (pkg_delete postgresql-7.2.3  
pkg_delete postgresql-devel-7.3.rc1 ; this is a FreeBSD box), then 
installed 7.3.  But I did not first stop the postmaster.  Then I ran 
initdb, and the first message was:

###
initdb: The directory /usr/local/pgsql/data exists but is not empty.
If you want to create a new database system, either remove or empty
the directory /usr/local/pgsql/data or run initdb with
an argument other than /usr/local/pgsql/data.
###

So I moved it out of the way: 
# mv  /usr/local/pgsql/data  /usr/local/pgsql/data.old

That's when I encountered the message mentioned in the subject.

The solution involved:

# mv /usr/local/pgsql/data.old /usr/local/pgsql/data
# /usr/local/etc/rc.d/010.pgsql.sh stop
# mv  /usr/local/pgsql/data  /usr/local/pgsql/data.old
# su -l pgsql -c initdb

Then the initdb ran successfully.

-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

[HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

We support alter table add foreign key.  How about supporting 
alter table drop foreign key?

- he said as he went to drop a foreign key
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 8:20, Stephan Szabo wrote:

 
 On Thu, 5 Dec 2002, Dan Langille wrote:
 
  We support alter table add foreign key.  How about supporting
  alter table drop foreign key?
 
  - he said as he went to drop a foreign key
 
 It seems to work for me on my 7.3b2 system with
 alter table table drop constraint constraint name;

How was that FK added?  How did you determine the constraint name?
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 8:20, Stephan Szabo wrote:

 
 On Thu, 5 Dec 2002, Dan Langille wrote:
 
  We support alter table add foreign key.  How about supporting
  alter table drop foreign key?
 
  - he said as he went to drop a foreign key
 
 It seems to work for me on my 7.3b2 system with
 alter table table drop constraint constraint name;

Premature send.. sorry

How was that FK added?  How did you determine the constraint name?

How would you do that if the FK was added with the following syntax?

alter table table
add foreign key (column)
   references othertable (othercolumn) 
on update cascade on delete cascade;


-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 8:44, Stephan Szabo wrote:

 On Thu, 5 Dec 2002, Dan Langille wrote:
 
  On 5 Dec 2002 at 8:20, Stephan Szabo wrote:
 
  
   On Thu, 5 Dec 2002, Dan Langille wrote:
  
We support alter table add foreign key.  How about supporting
alter table drop foreign key?
   
- he said as he went to drop a foreign key
  
   It seems to work for me on my 7.3b2 system with
   alter table table drop constraint constraint name;
 
  Premature send.. sorry
 
  How was that FK added?  How did you determine the constraint name?
 
 alter table table add constraint name foreign key ...
 
  How would you do that if the FK was added with the following syntax?
 
  alter table table
  add foreign key (column)
 references othertable (othercolumn)
  on update cascade on delete cascade;
 
 IIRC, the constraint will get an automatic name of the form
 $n in such cases.  I believe if you do a \d on the table,
 it gives the name in the constraint definitions (on one of mine
 i get:
 
 Foreign Key constraints: $1 FOREIGN KEY (a) REFERENCES qqq(a) ON UPDATE
 CASCADE ON DELETE NO ACTION
 
 Where $1 is the name of the constraint.

Thanks.  In my 7.2.3 database, the table in question has:

Primary key: watch_list_staging_pkey
Check constraints: watch_list_stag_from_watch_list 
((from_watch_list = 't'::bool) OR (from_watch_list = 'f'::bool))
   watch_list_stagin_from_pkg_info ((from_pkg_info 
= 't'::bool) OR (from_pkg_info = 'f'::bool))
Triggers: RI_ConstraintTrigger_4278482,
  RI_ConstraintTrigger_4278488

No mention of FK constraints.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 11:47, Dan Langille wrote:

 On 5 Dec 2002 at 8:44, Stephan Szabo wrote:
 
  On Thu, 5 Dec 2002, Dan Langille wrote:
  
   On 5 Dec 2002 at 8:20, Stephan Szabo wrote:
  
   
On Thu, 5 Dec 2002, Dan Langille wrote:
   
 We support alter table add foreign key.  How about supporting
 alter table drop foreign key?

 - he said as he went to drop a foreign key
   
It seems to work for me on my 7.3b2 system with
alter table table drop constraint constraint name;
  
   Premature send.. sorry
  
   How was that FK added?  How did you determine the constraint name?
  
  alter table table add constraint name foreign key ...
  
   How would you do that if the FK was added with the following syntax?
  
   alter table table
   add foreign key (column)
  references othertable (othercolumn)
   on update cascade on delete cascade;
  
  IIRC, the constraint will get an automatic name of the form
  $n in such cases.  I believe if you do a \d on the table,
  it gives the name in the constraint definitions (on one of mine
  i get:
  
  Foreign Key constraints: $1 FOREIGN KEY (a) REFERENCES qqq(a) ON UPDATE
  CASCADE ON DELETE NO ACTION
  
  Where $1 is the name of the constraint.
 
 Thanks.  In my 7.2.3 database, the table in question has:
 
 Primary key: watch_list_staging_pkey
 Check constraints: watch_list_stag_from_watch_list 
 ((from_watch_list = 't'::bool) OR (from_watch_list = 'f'::bool))
watch_list_stagin_from_pkg_info ((from_pkg_info 
 = 't'::bool) OR (from_pkg_info = 'f'::bool))
 Triggers: RI_ConstraintTrigger_4278482,
   RI_ConstraintTrigger_4278488
 
 No mention of FK constraints.

Found the solution:

drop trigger RI_ConstraintTrigger_4278488 on watch_list_staging;

Given that the FK in question did not have a name to start with, I 
concede that it would be difficult to code DROP FOREIGN KEY.

What about supporting ALTER TABLE table ADD FOREIGN KEY keyname 
... which at present we don't?  That would then make dropping the FK 
a simple coding issue?
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 9:02, Stephan Szabo wrote:

 On Thu, 5 Dec 2002, Dan Langille wrote:
 
  Found the solution:
 
  drop trigger RI_ConstraintTrigger_4278488 on watch_list_staging;
 
 Actually there are three triggers for the constraint.  You may have
 dangling triggers on the other table of the constraint.  It's one on the
 table the constraint's defined on and two on the referenced table.
 
  Given that the FK in question did not have a name to start with, I
  concede that it would be difficult to code DROP FOREIGN KEY.
 
  What about supporting ALTER TABLE table ADD FOREIGN KEY keyname
  ... which at present we don't?  That would then make dropping the FK
  a simple coding issue?
 
 ISTM, that's
  ALTER TABLE table ADD CONSTRAINT name FOREIGN KEY ...
 which should be there in any 7.x.

Agreed.  But the syntax is different. If we are supporting ALTER 
TABLE table ADD FOREIGN KEY  without a name, why not support it 
with a name?

 And the drop constraint for foreign keys (and the \d display stuff) is new
 in 7.3.

That's going to be much more useful.  I installed 7.3 for testing 
this morning.  Looking at it now, I no longer see a need for a DROP 
FOREIGN KEY. 

Thank you.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 9:31, Stephan Szabo wrote:

 When we talk about ALTER TABLE ADD FOREIGN KEY we're being imprecise, so
 I think that might be why we're talking past each other here.
 
 Technically the syntax in question is:
  ALTER TABLE table ADD table constraint definition
 where CONSTRAINT name is an optional leading clause in a table
 constraint definition.  ADD FOREIGN KEY is a shorthand for a foreign key
 constraint (technically unnamed).

Understood.

What about allowing a named foreign key?  I haven't checked the RFCs

 Thus you can also say things like:
 ALTER TABLE table ADD CONSTRAINT blah CHECK (foo!=0);
 to make a named check constraint.

Understood.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 9:51, Stephan Szabo wrote:

 On Thu, 5 Dec 2002, Dan Langille wrote:
 
  On 5 Dec 2002 at 9:31, Stephan Szabo wrote:
 
   When we talk about ALTER TABLE ADD FOREIGN KEY we're being imprecise, so
   I think that might be why we're talking past each other here.
  
   Technically the syntax in question is:
ALTER TABLE table ADD table constraint definition
   where CONSTRAINT name is an optional leading clause in a table
   constraint definition.  ADD FOREIGN KEY is a shorthand for a foreign key
   constraint (technically unnamed).
 
  Understood.
 
  What about allowing a named foreign key?  I haven't checked the RFCs
 
 Here's a part of what SQL92 (draft) has to say about table constraint
 definitions:
 
  table constraint definition ::=
   [ constraint name definition ]
   table constraint [ constraint attributes ]
 
  table constraint ::=
 unique constraint definition
   | referential constraint definition
   | check constraint definition
 
 
  constraint name definition ::= CONSTRAINT constraint name
 
  referential constraint definition ::=
   FOREIGN KEY left paren referencing columns right paren
 references specification
 
 11.6 Syntax Rules
 
  2) If constraint name definition is not specified, then a con-
 straint name definition that contains an implementation-
 dependent constraint name is implicit. The assigned con-
 straint name shall obey the Syntax Rules of an explicit con-
 straint name.
 
 In our case, the implementation dependent naming scheme is I believe
 $n where n is the maximum one already there for that table +1 I
 would guess.

Thanks.  I guess I should rename my thread to 7.4 - TODO : allow 
constraint names when using the ALTER TABLE table ADD FOREIGN KEY 
syntax.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [HACKERS] contrib/ltree patches

[Dan Langille]

Thanks for asking.  I have been diverted to other tasks and won't be 
able to get back to this for a short while.  The basics work (i.e. 
population and simple compares) but I know for sure that certain 
functions will not work now that we allow what were previously 
operators to be part of the node name.  In short, the code needs to 
allow for operators to be escaped if they are part of the node name.

On 5 Dec 2002 at 0:54, Bruce Momjian wrote:

 
 Dan, is this ready to be applied to CVS?
 
 --
 -
 
 Dan Langille wrote:
  I have been looking at contrib/ltree in the PostgreSQL repository. 
  I've modified the code to allow / as a node delimiter instead of .
  which is the default.
  
  Below are the patches to make this change.  I have also moved the
  delimiter to a DEFINE so that other customizations are easily done. 
  This is a work in progress.
  
  My thanks to DarbyD for assistance.
  
  cheers
  
  
  --- ltree.h.origTue Nov 26 18:57:58 2002
  +++ ltree.h Tue Nov 26 20:16:40 2002
  @@ -6,6 +6,8 @@
   #include utils/palloc.h
   #include utils/builtins.h
  
  +#defineNODE_DELIMITER  '/'
  +
   typedef struct
   {
  uint8   len;
  @@ -88,7 +90,7 @@
   #ifndef abs
   #define abs(a) ((a)   (0) ? -(a) : (a))
   #endif
  -#define ISALNUM(x) ( isalnum((unsigned int)(x)) || (x) == '_' )
  +#define ISALNUM(x) ( isalnum((unsigned int)(x)) || (x) == '_' ||
  +#(x) == NODE_DELIMITER )
  
   /* full text query */
  
  --- ltree_io.c  Tue Nov 26 20:23:45 2002
  +++ ltree_io.c.orig Tue Nov 26 18:57:26 2002
  @@ -48,7 +48,7 @@
  ptr = buf;
  while (*ptr)
  {
  -   if (*ptr == NODE_DELIMITER)
  +   if (*ptr == '.')
  num++;
  ptr++;
  }
  @@ -69,7 +69,7 @@
  }
  else if (state == LTPRS_WAITDELIM)
  {
  -   if (*ptr == NODE_DELIMITER)
  +   if (*ptr == '.')
  {
  lptr-len = ptr - lptr-start;
  if (lptr-len  255)
  @@ -131,7 +131,7 @@
  {
  if (i != 0)
  {
  -   *ptr = NODE_DELIMITER;
  +   *ptr = '.';
  ptr++;
  }
  memcpy(ptr, curlevel-name, curlevel-len);
  @@ -181,7 +181,7 @@
  ptr = buf;
  while (*ptr)
  {
  -   if (*ptr == NODE_DELIMITER)
  +   if (*ptr == '.')
  num++;
  else if (*ptr == '|')
  numOR++;
  @@ -265,7 +265,7 @@
   lptr-len, (int) (lptr-start - buf));
  state = LQPRS_WAITVAR;
  }
  -   else if (*ptr == NODE_DELIMITER)
  +   else if (*ptr == '.')
  {
  lptr-len = ptr - lptr-start -
  ((lptr-flag  LVAR_SUBLEXEM) ? 1 : 0) -
  @@ -289,7 +289,7 @@
  {
  if (*ptr == '{')
  state = LQPRS_WAITFNUM;
  -   else if (*ptr == NODE_DELIMITER)
  +   else if (*ptr == '.')
  {
  curqlevel-low = 0;
  curqlevel-high = 0x;
  @@ -347,7 +347,7 @@
  }
  else if (state == LQPRS_WAITEND)
  {
  -   if (*ptr == NODE_DELIMITER)
  +   if (*ptr == '.')
  {
  state = LQPRS_WAITLEVEL;
  curqlevel = NEXTLEV(curqlevel);
  @@ -471,7 +471,7 @@
  {
  if (i != 0)
  {
  -   *ptr = NODE_DELIMITER;
  +   *ptr = '.';
  ptr++;
  }
  if (curqlevel-numvar)
  
  
  ---(end of
  broadcast)--- TIP 4: Don't 'kill -9' the
  postmaster
  
 
 -- 
   Bruce Momjian|  http://candle.pha.pa.us
   [EMAIL PROTECTED]   |  (610) 359-1001 +  If your
   life is a hard drive, |  13 Roberts Road +  Christ can be your
   backup.|  Newtown Square, Pennsylvania 19073
 


-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 14:17, Fernando Nasser wrote:

 Dan Langille wrote: On 5 Dec 2002 at 11:47, Dan Langille wrote:
  
  drop trigger RI_ConstraintTrigger_4278488 on watch_list_staging;
  
 
 You should now go to the table this RI constraint was referring to and delete 
 the two triggers in there as well.  They will still be checking for deletions 
 and updates.  Look for something like
 RI_ConstraintTrigger_4278490
 RI_ConstraintTrigger_4278492
 and with the associated procedure RI_FKey_noaction_del and RI_FKey_noaction_upd

Oh thank you!  I didn't know about those.  FWIW, I've just documented 
this exercise at http://www.freebsddiary.org/postgresql-dropping-
constraints.php so corrections are most welcome.

 BTW, the rhdb-admin program can drop the constraints for you, even the unnamed 
 ones on backends 7.2 up.  You can download it from:
 
 http://sources.redhat.com/rhdb

Thanks.  I hope to check that out one day.

 Of course, now that you broke the set of triggers for this FK constraint you'll 
 still need to drop the other ones by hand.  But the tool at least will show you 
 the column and table involved so it will be easier to identify the two you have 
 to get rid of.

I did the identification by hand and fixed it up that way. Hopefully 
there's nothing else in there I've done wrong.

-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 11:52, Christopher Kings-Lynne wrote:

Thanks.  I guess I should rename my thread to 7.4 - TODO : allow
constraint names when using the ALTER TABLE table ADD FOREIGN KEY
syntax.
  
   You can do that now.
  
   ALTER TABLE table ADD CONSTRAINT const FOREIGN KEY 
 
  That I know.  That syntax is radically different from that proposed.

I take back the adjective radical 

 Isn't it identical?  The CONSTRAINT const is SQL standard optional clause
 for all commands that add constraints.

Except that one is ADD CONSTRAINT, the other is an ADD FOREIGN KEY. 
They are similar in nature but different overall.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 12:09, Christopher Kings-Lynne wrote:

   Isn't it identical?  The CONSTRAINT const is SQL standard optional
 clause
   for all commands that add constraints.
 
  Except that one is ADD CONSTRAINT, the other is an ADD FOREIGN KEY.
  They are similar in nature but different overall.
 
 I think you're getting a little confused here, Dan.
 
 http://www3.us.postgresql.org/users-lounge/docs/7.3/postgres/sql-altertable.
 html
 
 There is only one command for adding constraints to a table.  It has this
 syntax:
 
 ALTER TABLE [ ONLY ] table [ * ]
 ADD table_constraint
 
 The table_constraint clause is defined like this (basically):
 
 [CONSTRAINT blah] (PRIMARY KEY or UNIQUE or  FOREIGN KEY) ...
 
 So, the CONSTRAINT blah clause allows you to specify a name for any of the 3
 types of constraint: primary key, unique or foreign key.  There's nothing
 special about foreign keys in this case.
 
 If you don't put in the CONSTRAINT blah clause, you get an automatically
 assigned constraint name.

Regardless of what is documented, the following is valid and works:

ALTER TABLE slave
   ADD FOREIGN KEY (master_id)
   REFERENCES master (id) ON DELETE CASCADE;
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] 7.4 - TODO : alter table drop foreign key

[Dan Langille]

On 5 Dec 2002 at 15:36, Tom Lane wrote:

 Dan Langille [EMAIL PROTECTED] writes:
  You can do that now.
  ALTER TABLE table ADD CONSTRAINT const FOREIGN KEY 
 
  That I know.  That syntax is radically different from that proposed.
 
 So you're proposing we replace a SQL-spec-compliant syntax with one
 that is not?  Why?

If it's not compliant, I withdraw.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)

[Dan Langille]

On 3 Dec 2002 at 15:08, Vince Vielhaber wrote:

 Where have you been?  The lines of distinction between all of the
 lists have gotten so blurred it hardly makes a difference.

So consider this a wake up call.
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] 7.4 Wishlist

[Dan Langille]

Can you see this tying in with my recent hack of contrib/ltree to work
with a wider range of node names?

On Sat, 30 Nov 2002, Oleg Bartunov wrote:

 Me and Teodor hope to work on contrib/ltree to add support for sort of
 xml. Any ideas are welcome !


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] contrib/ltree patches

[Dan Langille]

On 27 Nov 2002 at 12:16, Teodor Sigaev wrote:

 Dan Langille wrote:
  I have been looking at contrib/ltree in the PostgreSQL repository. 
  I've modified the code to allow / as a node delimiter instead of .
  which is the default.

 What is the reason for changing delimiter?

My tree represents a file system.  Here are some entries:

# select id, pathname from element_pathnames order by pathname;
  77024 | doc/de_DE.ISO8859-1
  77028 | doc/de_DE.ISO8859-1/books
  84590 | doc/de_DE.ISO8859-1/books/Makefile.inc
  77029 | doc/de_DE.ISO8859-1/books/faq
  84591 | doc/de_DE.ISO8859-1/books/faq/Makefile
  77030 | doc/de_DE.ISO8859-1/books/faq/book.sgml
  77691 | doc/de_DE.ISO8859-1/books/handbook
  77704 | doc/de_DE.ISO8859-1/books/handbook/Makefile
110592 | doc/de_DE.ISO8859-1/books/handbook/advanced-networking

  Below are the patches to make this change.  I have also moved the
  delimiter to a DEFINE so that other customizations are easily done. 
  This is a work in progress.

 It's good.

Thank you.  More patches will follow as I get closer to my objective.

  -#define ISALNUM(x) ( isalnum((unsigned int)(x)) || (x) == '_' )
  +#define ISALNUM(x) ( isalnum((unsigned int)(x)) || (x) == '_' ||
  +#(x) == NODE_DELIMITER )

 It seems to me  that it's mistake. ISALNUM shoud define correct
 character in name of node (level).  Try to test with incorrect ltree
 value 'a..b'.

I just did some simple tests and I see what you mean:

ltree_test=# select * from tree;
 id | pathname
+--
  1 | /ports
  2 | ports/security
  2 | ports//security
  2 | /ports//security
  2 | a..b
(5 rows)

Then I removed NODE_DELIMITER from ISALNUM and tried again:

ltree_test=# insert into tree values (2, '/ports//security');
ERROR:  Syntax error in position 0 near '/'
ltree_test=# insert into tree values (2, 'ports//security');
ERROR:  Syntax error in position 6 near '/'
ltree_test=# insert into tree values (2, 'ports/security');
INSERT 29955201 1
ltree_test=# insert into tree values (2, 'ports/security/');
ERROR:  Unexpected end of line
ltree_test=# insert into tree values (2, 'ports/security/things');
INSERT 29955202 1

ltree_test=# select * from tree;
 id |   pathname
+---
  1 | /ports
  2 | ports/security
  2 | ports//security
  2 | /ports//security
  2 | a..b
  2 | ports/security
  2 | ports/security/things
(7 rows)

Removing NODE_DELIMITER from ISALNUM makes sense.  Thank you.  Here 
is the reason why NODE_DELIMITER was added. My initial data sample 
was of the form /usr/local/ (i.e. it started with a 
NODE_DELIMITER).  I have since changed my data so it does not start 
with a leading / because queries were not working.

Based upon the sample data I was using (approximately 120,000 nodes 
as taken from a real file system), I had to change ISALNUM as I went 
along.  Here is the current definition for ISALNUM:

#define ISALNUM(x)   ( isalnum((unsigned int)(x)) || (x) == '_' || 
(x) == '-' || (x) == '.' || (x) == '+' || (x) == ':' || (x) == '~' || 
(x) == '%' || (x) == ',' || (x) == '#')

Given that I am trying to allow any valid filename, I think ISALNUM 
needs to allow any ASCII character.

I also think I will need to modify the parsing within lquery_in to 
allow escaping of characters it recognizes but which may be part of a 
file name (e.g. :%~ may be part of a file name, but these are special 
characters to lquery_in).  That I think will be the biggest change.

Thank you for your interest and help.

-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] contrib/ltree patches

[Dan Langille]

On 27 Nov 2002 at 19:55, Teodor Sigaev wrote:

 Ok, I think it's a good extension. Let you prepare cumulative patch.
 Nevertheless, we have no chance to insert this to 7.3 release :(. 
 Only for 7.3.1 or even 7.4.

Thanks.  As for the 7.3 release, yes, it would be nice, but that was 
not my goal.  :)
-- 
Dan Langille : http://www.langille.org/


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

[HACKERS] contrib/ltree patches

[Dan Langille]

I have been looking at contrib/ltree in the PostgreSQL repository.  I've
modified the code to allow / as a node delimiter instead of . which is the
default.

Below are the patches to make this change.  I have also moved the
delimiter to a DEFINE so that other customizations are easily done.  This
is a work in progress.

My thanks to DarbyD for assistance.

cheers


--- ltree.h.origTue Nov 26 18:57:58 2002
+++ ltree.h Tue Nov 26 20:16:40 2002
@@ -6,6 +6,8 @@
 #include utils/palloc.h
 #include utils/builtins.h

+#defineNODE_DELIMITER  '/'
+
 typedef struct
 {
uint8   len;
@@ -88,7 +90,7 @@
 #ifndef abs
 #define abs(a) ((a)   (0) ? -(a) : (a))
 #endif
-#define ISALNUM(x) ( isalnum((unsigned int)(x)) || (x) == '_' )
+#define ISALNUM(x) ( isalnum((unsigned int)(x)) || (x) == '_' || (x) == 
+NODE_DELIMITER )

 /* full text query */

--- ltree_io.c  Tue Nov 26 20:23:45 2002
+++ ltree_io.c.orig Tue Nov 26 18:57:26 2002
@@ -48,7 +48,7 @@
ptr = buf;
while (*ptr)
{
-   if (*ptr == NODE_DELIMITER)
+   if (*ptr == '.')
num++;
ptr++;
}
@@ -69,7 +69,7 @@
}
else if (state == LTPRS_WAITDELIM)
{
-   if (*ptr == NODE_DELIMITER)
+   if (*ptr == '.')
{
lptr-len = ptr - lptr-start;
if (lptr-len  255)
@@ -131,7 +131,7 @@
{
if (i != 0)
{
-   *ptr = NODE_DELIMITER;
+   *ptr = '.';
ptr++;
}
memcpy(ptr, curlevel-name, curlevel-len);
@@ -181,7 +181,7 @@
ptr = buf;
while (*ptr)
{
-   if (*ptr == NODE_DELIMITER)
+   if (*ptr == '.')
num++;
else if (*ptr == '|')
numOR++;
@@ -265,7 +265,7 @@
 lptr-len, (int) (lptr-start - buf));
state = LQPRS_WAITVAR;
}
-   else if (*ptr == NODE_DELIMITER)
+   else if (*ptr == '.')
{
lptr-len = ptr - lptr-start -
((lptr-flag  LVAR_SUBLEXEM) ? 1 : 0) -
@@ -289,7 +289,7 @@
{
if (*ptr == '{')
state = LQPRS_WAITFNUM;
-   else if (*ptr == NODE_DELIMITER)
+   else if (*ptr == '.')
{
curqlevel-low = 0;
curqlevel-high = 0x;
@@ -347,7 +347,7 @@
}
else if (state == LQPRS_WAITEND)
{
-   if (*ptr == NODE_DELIMITER)
+   if (*ptr == '.')
{
state = LQPRS_WAITLEVEL;
curqlevel = NEXTLEV(curqlevel);
@@ -471,7 +471,7 @@
{
if (i != 0)
{
-   *ptr = NODE_DELIMITER;
+   *ptr = '.';
ptr++;
}
if (curqlevel-numvar)


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] (Fwd) Re: Any Oracle 9 users? A test please...

[Dan Langille]

The original tester says this is an anonymous procedure.

On 30 Sep 2002 at 15:07, Bruce Momjian wrote:

 
 It is not clear to me;  is this its own transaction or a function
 call?
 
 --
 -
 
 Dan Langille wrote:
  And just for another opinion, which supports the first.
  
  From now, unless you indicate otherwise, I'll only report tests
  which 
  have both values the same.
  
  From: Shawn O'Connor [EMAIL PROTECTED]
  To: Dan Langille [EMAIL PROTECTED]
  Subject: Re: Any Oracle 9 users?  A test please...
  In-Reply-To: 3D985663.24174.80554E83@localhost
  Message-ID: [EMAIL PROTECTED]
  MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII
  X-PMFLAGS: 35127424 0 1 P2A7A0.CNM
  
  Okay, here you are:
  --
  
  DECLARE
   time1 TIMESTAMP;
   time2 TIMESTAMP;
   sleeptime NUMBER;
  BEGIN
   sleeptime := 5;
   SELECT CURRENT_TIMESTAMP INTO time1 FROM DUAL;
   DBMS_LOCK.SLEEP(sleeptime);
   SELECT CURRENT_TIMESTAMP INTO time2 FROM DUAL;
   DBMS_OUTPUT.PUT_LINE(TO_CHAR(time1));
   DBMS_OUTPUT.PUT_LINE(TO_CHAR(time2));
  END;
  /
  30-SEP-02 11.54.09.583576 AM
  30-SEP-02 11.54.14.708333 AM
  
  PL/SQL procedure successfully completed.
  
  --
  
  Hope this helps!
  
   -Shawn
  
  
  On Mon, 30 Sep 2002, Dan Langille wrote:
  
   We're testing this just to see what Oracle does.  What you are
   saying is what we expect to happen.  But could you do that test
   for us from the command line?  Thanks.
  
   On 30 Sep 2002 at 10:31, Shawn O'Connor wrote:
  
I'm assuming your doing this as some sort of anonymous
PL/SQL function:
   
Don't you need to do something like:
   
SELECT CURRENT_TIMESTAMP FROM DUAL INTO somevariable?
   
and to wait five seconds probably:
   
EXECUTE DBMS_LOCK.SLEEP(5);
   
But to answer your question-- When this PL/SQL function
is run the values of current_timestamp are not the same, they
will be sepearated by five seconds or so.
   
Hope this helps!
   
 -Shawn
   
On Mon, 30 Sep 2002, Dan Langille wrote:
   
 Followups to [EMAIL PROTECTED] please!

 Any Oracle 9 users out there?

 I need this run:

 BEGIN;
 SELECT CURRENT_TIMESTAMP;
 -- wait 5 seconds
 SELECT CURRENT_TIMESTAMP;

 Are those two timestamps the same?

 Thanks
 --
 Dan Langille
 I'm looking for a computer job:
 http://www.freebsddiary.org/dan_langille.php


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-database in the body of the message

   
   
  
  
   --
   Dan Langille
   I'm looking for a computer job:
   http://www.freebsddiary.org/dan_langille.php
  
  
  
  --- End of forwarded message ---
  -- 
  Dan Langille
  I'm looking for a computer job:
  http://www.freebsddiary.org/dan_langille.php
  
  
 
 -- 
   Bruce Momjian|  http://candle.pha.pa.us
   [EMAIL PROTECTED]   |  (610) 359-1001 +  If your
   life is a hard drive, |  13 Roberts Road +  Christ can be your
   backup.|  Newtown Square, Pennsylvania 19073
 


-- 
Dan Langille
I'm looking for a computer job:
http://www.freebsddiary.org/dan_langille.php


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

[HACKERS] GET DIAGNOSTICS SELECT PROCESSED INTO int4_variable

[Dan Langille]

Does anyone know if this feature exists?  If so, what version or where 
can a patch be obtained?

Thanks

--- Forwarded message follows ---
Date sent:  Mon, 15 Jan 2001 08:44:46 +0100
From:   "J.H.M. Dassen (Ray)" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject:Re: getting number of rows updated within a procedure

On Sun, Jan 14, 2001 at 23:27:06 +1300, Dan Langille wrote:
 I'm writing some stuff in PL/pgsql (actually, a lot of stuff).  I have a
 question: At various times, it does UPDATEs.  Is there a way to tell if
 the UPDATE actually affected any rows or not?  I couldn't see how to get
 UPDATE to return anything.
  
Quoting a recent message by Jan Wieck [EMAIL PROTECTED]:
:Do a
:
:GET DIAGNOSTICS SELECT PROCESSED INTO int4_variable;  
:
:directly  after  an  INSERT,  UPDATE  or DELETE statement and you'll know
:how many rows have been hit.
:
:Also you can get the OID of an inserted row with
:
:GET DIAGNOSTICS SELECT RESULT INTO int4_variable;

HTH,
Ray
-- 
"The software `wizard' is the single greatest obstacle to computer literacy
since the Mac."
http://www.osopinion.com/Opinions/MichaelKellen/MichaelKellen1.html
--- End of forwarded message ---

--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/
   FreshPorts - http://freshports.org/
 NZ Broadband - http://unixathome.org/broadband/