--On Montag, September 04, 2006 23:58:35 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Updatable views are likewise dead --- we don't have a credible patch or
any short-term path to get one. I hope to see both of these items land
early in the 8.3 devel cycle, but for 8.2, nyet.
Yeah, i don't had
Chris Browne wrote:
I also seem to recall, in past discussions about library matters,
that AIX is more sticky about requiring that libraries be named
expressly.
ecpglib has
SHLIB_LINK = -L../pgtypeslib -lpgtypes $(libpq) \
$(filter -lintl -lssl -lcrypto -lkrb5 -lcrypt -lm, $(LIBS))
Yes they are using a connection pool. A java based one.
Since java has it's own protocol implementation, this is
totally
unrelated to any libpq error messages.
Another important point that we've not been given information
on:
when pgAdmin/libpq starts failing like this, exactly what is
Magnus Hagander wrote:
Another point that at least I don't know - what kind of connection pool
is it? Is it an external one (like pgpool) to which the java app
connects (using FE/BE protocol, emulating a proper postmaster but
pooling access to the database), or is it running inside the app
The existing geometric containment tests seem to be nonstrict, so
if
we wanted to leave room to add strict ones later, it might be best
to
settle on
x @= yx contains or equals y
x =@ yx is contained in or equals y
reserving @ and @ for future strict
Tom Lane wrote:
The existing geometric containment tests seem to be nonstrict, so if we
wanted to leave room to add strict ones later, it might be best to
settle on
x @= y x contains or equals y
x =@ y x is contained in or equals y
reserving @ and @
Am Dienstag, 5. September 2006 05:58 schrieb Tom Lane:
A couple of recently discussed FE/BE protocol issues are: not storing a
plan at all for unnamed-statement cases, and thus allowing bind
parameters to be treated as constants; allowing parameter types to go
unresolved rather than throwing
Am Dienstag, 5. September 2006 03:07 schrieb Bruce Momjian:
Here are the open items for 8.2:
http://momjian.postgresql.org/cgi-bin/pgopenitems
This host seems to be offline. What about using the wiki?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Hello,
On Wed, 2006-09-06 at 13:04 +0200, Peter Eisentraut wrote:
http://momjian.postgresql.org/cgi-bin/pgopenitems
This host seems to be offline.
It is suffering from a DNS problem.
What about using the wiki?
Wiki has the same problem, too.
Regards,
--
The PostgreSQL Company
Hi,
Warthog has been failing for the last 12 hours or so on contrib/sslinfo
It seems that readline and termcap should not be linked with.
What can I do to help?
Also, now that beta is approaching, warthog runs his HEAD buikd every 8
hours. Do we need it more often?
Regards,
--
Olivier
Sorry to ask this question here...
How do I include newly created files in a patch with difforig or patch
Thank you.
---(end of broadcast)---
TIP 6: explain analyze is your friend
Michael, if you want shell access to guppy, just contact me privately.
Warning: guppy too, is somewhat dated (1:10 hours for the make step) :/
Michael,
did you receive my private mail yesterday?
(just want to make sure it wasn't blocked by an overzealous spam filter)
Bye, Chris.
--
Chris
On Wed, Sep 06, 2006 at 01:32:53PM +0200, ohp@pyrenet.fr wrote:
Hi,
Warthog has been failing for the last 12 hours or so on contrib/sslinfo
It seems that readline and termcap should not be linked with.
What can I do to help?
Classic putting-non-PIC-code-in-a-shared-library error. You
On Wed, Sep 06, 2006 at 01:37:51PM +0200, Gevik Babakhani wrote:
Sorry to ask this question here...
How do I include newly created files in a patch with difforig or patch
Thank you.
The -N option to diff treats non-existant files as empty. So diff
-crN should do it.
Have you read the
Here are the open items for 8.2:
http://momjian.postgresql.org/cgi-bin/pgopenitems
This host seems to be offline. What about using the wiki?
The problem is with the postgresql.org DNS servers. Something weird is
afoot around the hub.org nameservers, from what I can tell. Servers
On 6-Sep-06, at 3:27 AM, Magnus Hagander wrote:
Yes they are using a connection pool. A java based one.
Since java has it's own protocol implementation, this is
totally
unrelated to any libpq error messages.
Another important point that we've not been given information
on:
when
It seems ECPG regression tests trigger a bug in OpenBSD libc. Please try
the attached test case. I should give ERANGE as error, but on OpenBSD
errno is set to 0.
I tried this test case on Linux, where it works, and OpenBSD 3.8 and 4.0
(that is HEAD). On both these systems it doesn't. Now the
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Magnus
Hagander) wrote:
Here are the open items for 8.2:
http://momjian.postgresql.org/cgi-bin/pgopenitems
This host seems to be offline. What about using the wiki?
The problem is with the postgresql.org DNS servers.
Zeugswetter Andreas DCP SD [EMAIL PROTECTED] writes:
Hm, I've never seen anyone spell less than or equal to as
=, so I'm not sure where you derive =@ from? Not
saying no, but the other seems clearer to me.
Yes, but to me too =@ seems more natural since we started with @ and @.
Tom, your
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Dienstag, 5. September 2006 05:58 schrieb Tom Lane:
A couple of recently discussed FE/BE protocol issues are: not storing a
plan at all for unnamed-statement cases, and thus allowing bind
parameters to be treated as constants; allowing parameter
Peter Eisentraut wrote:
Am Dienstag, 5. September 2006 03:07 schrieb Bruce Momjian:
Here are the open items for 8.2:
http://momjian.postgresql.org/cgi-bin/pgopenitems
This host seems to be offline. What about using the wiki?
The host is fine. postgresql.org DNS is broken.
Simon Riggs wrote:
On Sat, 2006-09-02 at 09:14 -0400, Bruce Momjian wrote:
Simon Riggs wrote:
OK, I'll submit a C program called pg_standby so that we have an
approved and portable version of the script, allowing it to be
documented more easily.
I think we are still waiting
Zeugswetter Andreas DCP SD wrote:
The existing geometric containment tests seem to be nonstrict, so
if
we wanted to leave room to add strict ones later, it might be best
to
settle on
x @= y x contains or equals y
x =@ y x is contained in or equals y
Bruce Momjian wrote:
Tom Lane wrote:
Had a bitmap-index patch arrived in my inbox this morning, as had been
promised to me for three weekends running, I might have been willing to
drop all else and review it. But, no patch. This item is dead for 8.2.
Do not even think of suggesting otherwise.
On Wed, Aug 30, 2006 at 12:48:55PM -0400, Chris Browne wrote:
This looks like you're using an old version of the parser. preproc.y was
changed to handle empty database names and the the error you report is
due to an empty db name.
I think the problem is that the latest version of
Magnus Hagander wrote:
Yes, there are DNS issues. They are partly solved, but expect further
hiccups for a while.
Seems the PostgreSQL master DNS servers became unavailable sometime in
the past few hours, and Larry's secondary DNS was not responding because
it had stale data.
I told Larry to
Greetings,
* Tom Lane ([EMAIL PROTECTED]) wrote:
Does anyone have examples of real user-defined types that would need two
fields? If not it may not be worth spending time on.
Guess I'm jumping in a little late on this, but when reading the threads
linked to from the TODO items on user-defined
Michael Meskes wrote:
It seems ECPG regression tests trigger a bug in OpenBSD libc. Please try
the attached test case. I should give ERANGE as error, but on OpenBSD
errno is set to 0.
I tried this test case on Linux, where it works, and OpenBSD 3.8 and 4.0
(that is HEAD). On both these
On Sun, Sep 03, 2006 at 07:42:02PM -0400, Tom Lane wrote:
The hard part of this problem is finding a convenient way to capture
status data out of the community's conversations. I think when you find
a solution to that, you'll notice that email is not the problem.
In private groups (like
On Tue, 2006-09-05 at 23:00 -0400, Tom Lane wrote:
Jeff Davis [EMAIL PROTECTED] writes:
On Mon, 2006-09-04 at 10:45 -0400, Tom Lane wrote:
The existing geometric containment tests seem to be nonstrict, so if we
wanted to leave room to add strict ones later, it might be best to
settle on
Removing
#include $(top_srcdir)/contrib/contrib-global.mk
in sslinfo Makefile makes the problem go away...
Hope it helps
On Wed, 6 Sep 2006, Martijn van Oosterhout wrote:
Date: Wed, 6 Sep 2006 13:49:21 +0200
From: Martijn van Oosterhout kleptog@svana.org
To: ohp@pyrenet.fr
Cc: pgsql-hackers
On Tue, 2006-09-05 at 23:28 -0400, [EMAIL PROTECTED] wrote:
On Tue, Sep 05, 2006 at 05:54:50PM -0700, Jeff Davis wrote:
On Tue, 2006-09-05 at 18:24 -0400, Chris Browne wrote:
Recently seen in ACM Operating Systems Review (this is the first time
I've found as many as 1 interesting article
On Sat, 2006-09-02 at 09:14 -0400, Bruce Momjian wrote:
Simon Riggs wrote:
OK, I'll submit a C program called pg_standby so that we have an
approved and portable version of the script, allowing it to be
documented more easily.
I think we are still waiting for this. I am also waiting
Andrew Sullivan wrote:
On Sun, Sep 03, 2006 at 07:42:02PM -0400, Tom Lane wrote:
The hard part of this problem is finding a convenient way to capture
status data out of the community's conversations. I think when you find
a solution to that, you'll notice that email is not the problem.
I would like to know if anyone is working on the GUID datatype.
If not, I am going to work on it. Please let me know.
Regards,
Gevik.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Wed, Sep 06, 2006 at 12:50:20PM -0400, Stephen Frost wrote:
The information for each attribute is:
Number of dimensions
Spatial Referencing System (identified by the SRID)
Type (ie: Point, Polygon, etc)
snip
POINT(dims, srid) - eg: POINT(2,4269)
geometry(dims,
Any chance for a DB Client accessible list of allowable time zones? I've
been told that the only way to get at this list is by looking through
the source and lifting the list from zone.tab.
While I'm at it, how about an accessible list of country codes? I know
that it's not core db
On Thu, Sep 07, 2006 at 04:07:58AM +1000, Naz Gassiep wrote:
Any chance for a DB Client accessible list of allowable time zones? I've
been told that the only way to get at this list is by looking through
the source and lifting the list from zone.tab.
In the CVS version there is a table with
Martijn van Oosterhout wrote:
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Great, thanks for that
Err, where does postgres use this information? I beleive there is a
project on pgfoundary that has
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Dienstag, 5. September 2006 05:58 schrieb Tom Lane:
A couple of recently discussed FE/BE protocol issues are: not storing a
plan at all for unnamed-statement cases, and thus allowing bind
parameters to be treated as constants;
Naz Gassiep [EMAIL PROTECTED] writes:
Martijn van Oosterhout wrote:
Err, where does postgres use this information? I beleive there is a
project on pgfoundary that has some standard datasets.
Currently, it is stored in /src/timezone/data/iso3166.tab and I propose
to have it available in a
Martijn van Oosterhout kleptog@svana.org writes:
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Actually, what that view gives you is timezone offset abbreviations, not
the full zone names that you could use
Michael Meskes wrote:
It seems ECPG regression tests trigger a bug in OpenBSD libc. Please try
the attached test case. I should give ERANGE as error, but on OpenBSD
errno is set to 0.
I tried this test case on Linux, where it works, and OpenBSD 3.8 and 4.0
(that is HEAD). On both these
Actually, what that view gives you is timezone offset abbreviations, not
the full zone names that you could use with SET TIME ZONE. It strikes
me that we should have a view for that as well. We could use code
similar to scan_available_timezones() to generate the view output.
It's somewhat
Naz Gassiep [EMAIL PROTECTED] writes:
I don't know about anyone else, but the whole australian_timezones thing
seems like an ugly hackaround to me.
You really shouldn't be pontificating about this if you haven't been
paying attention to recent development work ;-)
Chris Browne [EMAIL PROTECTED] writes:
I still need the following, on AIX:
-SHLIB_LINK = $(libpq)
+SHLIB_LINK = $(libpq) $(LIBS)
No you don't --- see recent warthog complaint. We have to filter LIBS
down to just the minimum.
regards, tom lane
Joshua D. Drake [EMAIL PROTECTED] writes:
O.k. to recap:
This message will present itself, if connection attempts are made from the Web
Application (Java/JDBC), or locally via PgAdmin. Once the error message is
received, all subsequent connection attempts will also result in that same
I wrote:
Andrew - Supernews [EMAIL PROTECTED] writes:
I believe this could usefully (and transparently to clients) be changed
so that Bind on the unnamed statement does _not_ store the plan back in
the unnamed statement's context, but instead produces a plan which is
only used _for that
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.
html
Actually, what that view gives you is timezone offset
abbreviations, not the full zone names that you could use
with SET TIME ZONE. It strikes me
On Thu, Sep 07, 2006 at 05:29:04AM +1000, Naz Gassiep wrote:
I am also rather baffled at the way SAT is changed from being
interpreted as a day of the week in one mode, and a timezone in another.
Ugh. It'd be an argument if people actually used SAT as a timezone.
They don't, it's ACST.
Have
On Wed, Sep 06, 2006 at 09:13:34PM +0200, Stefan Kaltenbrunner wrote:
that hints that setting ERANGE on an underflow (vs an overflow) is
implementation specific though I ws unable to verify that this is indeed
the case ...
Odd, according to these references:
On Wed, Sep 06, 2006 at 07:49:09PM +0200, Gevik Babakhani wrote:
I would like to know if anyone is working on the GUID datatype.
If not, I am going to work on it. Please let me know.
Assuming you mean GUID in the same sense as UUID, there are many
non-core developers who would like to see it,
I happened to notice that the recently added code to log Bind-message
parameters was printing garbage into my log. On investigation it turned
out to be trying to print an already-pfree'd string. That's fixable,
but having looked at the code closely, I see a bunch of other stuff I'm
not happy
Magnus Hagander [EMAIL PROTECTED] writes:
Assuming we can sneak this in even though it's feature-freeze, want me
to look for it?
Yeah, please take a look --- seeing the size of the code will probably
help us decide if it's too late for 8.2 or not.
regards, tom lane
On 6-Sep-06, at 6:01 PM, Tom Lane wrote:
I happened to notice that the recently added code to log Bind-message
parameters was printing garbage into my log. On investigation it
turned
out to be trying to print an already-pfree'd string. That's fixable,
but having looked at the code
On Wed, Sep 06, 2006 at 11:20:12PM +0200, Martijn van Oosterhout wrote:
Odd, according to these references:
http://www.csse.uwa.edu.au/programming/ansic-library.html#stdlib
http://cplus.kompf.de/cliblist.html
http://docs.hp.com/en/B9106-90010/strtod.3C.html
returning ERANGE on underflow
On 6-Sep-06, at 6:17 PM, Tom Lane wrote:
Dave Cramer [EMAIL PROTECTED] writes:
On 6-Sep-06, at 6:01 PM, Tom Lane wrote:
* It doesn't log the values of parameters sent in binary mode, which
is something that at least JDBC needs.
AFAIK, we don't need binary mode right away, currently we
Tom Lane wrote:
I happened to notice that the recently added code to log Bind-message
parameters was printing garbage into my log. On investigation it turned
out to be trying to print an already-pfree'd string. That's fixable,
Uh, can you show me where?
but having looked at the code
Dave Cramer [EMAIL PROTECTED] writes:
On 6-Sep-06, at 6:01 PM, Tom Lane wrote:
* It doesn't log the values of parameters sent in binary mode, which
is something that at least JDBC needs.
AFAIK, we don't need binary mode right away, currently we only send
bytea parameters in binary mode
I
On Wed, 6 Sep 2006, Tom Lane wrote:
I thought somebody had mentioned that integers were also sent in binary
in the latest driver code? Can't find the archive entry right now though.
Using the fastpath protocol integers and oids are sent as binary. I don't
know if that is related to this
[EMAIL PROTECTED] (Jeff Davis) writes:
On Tue, 2006-09-05 at 23:28 -0400, [EMAIL PROTECTED] wrote:
On Tue, Sep 05, 2006 at 05:54:50PM -0700, Jeff Davis wrote:
On Tue, 2006-09-05 at 18:24 -0400, Chris Browne wrote:
Recently seen in ACM Operating Systems Review (this is the first time
I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane asked:
Superusers can access anything they want to. What's your point?
The spec says accessible ...
disclaimer
Not trying to lecture you Tom :), just posting my argument
here for others.
/disclaimer
Temp tables are special because the
I have added a modified version of this to the SGML documentation,
under data types.
---
bruce wrote:
Here is an new XML section for our SGML documentation. It explains the
various XML capabilities, if we support them,
Bruce Momjian wrote:
Robert Treat wrote:
FWIW I have never understood why we don't require patch submitters/committers
to update the release notes when they do the patch.
I've suggested this more than once in the past -- I think it would be a
clear improvement over the status quo. Updating
On Wed, 2006-09-06 at 18:55 -0400, Chris Browne wrote:
[EMAIL PROTECTED] (Jeff Davis) writes:
Do you see an advantage in using LFS for PostgreSQL?
Hey guys - I think the original poster only meant to suggest that it
was *interesting*... :-)
I see, my mistake.
From a
On 2006-09-06, Tom Lane [EMAIL PROTECTED] wrote:
Martijn van Oosterhout kleptog@svana.org writes:
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Actually, what that view gives you is timezone offset
On Wed, 6 Sep 2006, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Actually, what that view gives you is timezone offset abbreviations,
At 2006-09-06 18:01:38 -0400, [EMAIL PROTECTED] wrote:
That is, we'd log a Parse or Bind operation if it individually
exceeded the duration threshold, and not otherwise.
Ok.
If we've got support for logging the statement text and the parameter
values at Execute time, isn't logging the
On Mon, 4 Sep 2006, Dave Page wrote:
My understanding is that Gborg is being recovered from backup as I type.
I also understand that the delay was not caused by lack of backups or
anything similarly scary, but simply by other priorities.
Yes, I have the backup uploaded right now, and doing
Folks,
I'm not getting bug reports for 8.2 from inside Sun. However, I'm not sure
how I can determine from the source what build day a particular snapshot
instance is from -- sometimes these files get copied around a bit before
being built. Is there a file somewhere that would carry a
Gregory Stark wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
O.k. to recap:
This message will present itself, if connection attempts are made from the Web
Application (Java/JDBC), or locally via PgAdmin. Once the error message is
received, all subsequent connection attempts will also result
Joshua D. Drake wrote:
Gregory Stark wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
The only known resolution is to reboot Windows. Using the service
control panel to shutdown postgresql will fail once the message is
received. It is unknown if using the task master to individually
kill
[EMAIL PROTECTED] (Jeff Davis) wrote:
On Wed, 2006-09-06 at 18:55 -0400, Chris Browne wrote:
[EMAIL PROTECTED] (Jeff Davis) writes:
Do you see an advantage in using LFS for PostgreSQL?
Hey guys - I think the original poster only meant to suggest that it
was *interesting*... :-)
Michael Fuhr [EMAIL PROTECTED] writes:
In Plauger's _The Standard C Library_ (1992) on p 335 is an excerpt
from the standard (I think). At the end of a section entitled
7.10.1.4 The strtod function is the following: If the correct
value would cause underflow, zero is returned and the value
Gavin Sherry [EMAIL PROTECTED] writes:
It might seem a minor quibble, but it seems like a more reliable approach
might be to cast to a 64 bit type and user a 64 bit int formatter.
int64 is a real pain to use in error messages because of the
machine-dependence of the format string --- the
ereport(...errmsg(trouble at offset UINT64_FORMAT, bigintvar));
One more solution: add format code %D to expand_fmt_string() which should be
expanded to usual %d on 32-bit architecture and to UINT64_FORMAT on 64-bit.
--
Teodor Sigaev E-mail: [EMAIL
Teodor Sigaev [EMAIL PROTECTED] writes:
ereport(...errmsg(trouble at offset UINT64_FORMAT, bigintvar));
One more solution: add format code %D to expand_fmt_string() which should be
expanded to usual %d on 32-bit architecture and to UINT64_FORMAT on 64-bit.
Not very workable unless you can
On 9/5/06, Abhijit Menon-Sen [EMAIL PROTECTED] wrote:
At 2006-09-05 16:35:49 -0400, [EMAIL PROTECTED] wrote:
The biggest part of the work needed is to write the documentation ---
but we'd have to do that for Abhijit's patch too, since the userlocks
docs presumably fall under GPL along with
Josh Berkus josh@agliodbs.com writes:
I'm not getting bug reports for 8.2 from inside Sun. However, I'm not sure
how I can determine from the source what build day a particular snapshot
instance is from -- sometimes these files get copied around a bit before
being built. Is there a file
Tom,
Well, you could grep for the latest $PostgreSQL$ header line's commit
date, but I kinda wonder why exactly you should need to do that. If you
don't know when you pulled the snapshot you are testing, I submit you
have a process problem you ought to fix.
These aren't PostgreSQL test
At 2006-09-07 00:16:38 -0400, [EMAIL PROTECTED] wrote:
- Where would the code live, if it were in core?
- Shall I hack up the API you suggested in your earlier message?
are we still moving forward with this? I would love to see this go in
for 8.2.
I don't know about its going into 8.2 or
Josh,
Well, you could grep for the latest $PostgreSQL$ header line's commit
date, but I kinda wonder why exactly you should need to do that. If you
don't know when you pulled the snapshot you are testing, I submit you
have a process problem you ought to fix.
These aren't PostgreSQL
Josh Berkus wrote:
Josh,
Well, you could grep for the latest $PostgreSQL$ header line's commit
date, but I kinda wonder why exactly you should need to do that. If you
don't know when you pulled the snapshot you are testing, I submit you
have a process problem you ought to fix.
These aren't
Josh Berkus wrote:
Tom,
Well, you could grep for the latest $PostgreSQL$ header line's commit
date, but I kinda wonder why exactly you should need to do that. If you
don't know when you pulled the snapshot you are testing, I submit you
have a process problem you ought to fix.
These aren't
On Wed, 6 Sep 2006, Josh Berkus wrote:
Josh,
Well, you could grep for the latest $PostgreSQL$ header line's commit
date, but I kinda wonder why exactly you should need to do that. If you
don't know when you pulled the snapshot you are testing, I submit you
have a process problem you ought to
85 matches
Mail list logo
