Hmm, isn't 4h22m a LONG time for it even with clobbered cache?
All my tests so far have last less than 2h..
Regards
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges+33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64
On Wed, Nov 28, 2007 at 04:21:56PM -0700, Kris Jurka wrote:
Magnus Hagander wrote:
Where in the US? We generally list at least the state for ppl int he US
- most often both city+state. (shows up only for people listed as major
developers for the time being, which is why nobody asked for it
For archives, Tom commited the patch yesterday:
http://archives.postgresql.org/pgsql-committers/2007-11/msg00552.php
--
Guillaume
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
Tom Lane wrote:
I don't offhand see anything else I'd consider weakening the casting
rules for. If anyone else is interested, I took
...
substring(text,integer) |
substring(text,integer,integer) |
substring(text,text)
After reading the thread of 2004 regarding user quotas, I understand
why the discussion moved towards having a tablespace quota as a
solution.
My reason to start this discussion was due the need of controlling
database size. Having tablespace quotas could allow one to create a
database in a
On Wed, Nov 28, 2007 at 05:20:46PM +0100, Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 12:24:26PM -0300, Alvaro Herrera wrote:
Martijn van Oosterhout wrote:
On Wed, Nov 28, 2007 at 11:57:35AM -0300, Alvaro Herrera wrote:
Can we do something like this to report the Win32 error code so
+1
On Nov 29, 2007 4:09 AM, Andreas 'ads' Scherbaum [EMAIL PROTECTED]
wrote:
On Tue, 27 Nov 2007 15:37:04 -0500 Tom Lane wrote:
Andreas 'ads' Scherbaum [EMAIL PROTECTED] writes:
On Tue, 27 Nov 2007 11:08:58 -0800 Joshua D. Drake wrote:
Release 7.3.21 with and EOL addendum :). E.g; this
On Thu, Nov 29, 2007 at 09:09:47AM -0300, Alvaro Herrera wrote:
Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 05:20:46PM +0100, Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 12:24:26PM -0300, Alvaro Herrera wrote:
Martijn van Oosterhout wrote:
On Wed, Nov 28, 2007 at 11:57:35AM
On Thu, Nov 29, 2007 at 12:39:30AM -0500, Andrew Dunstan wrote:
The attached patch works for me to eliminate the errors. Please test ASAP.
tested, works for me:
#v+
# CREATE OR REPLACE FUNCTION test(TEXT) RETURNS bool language plperl as $$
return (shift =~ /[a-ząćęłńóśźżĄĆĘŁŃŚÓŹŻ0-9_-]+/i) || 0;
Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 05:20:46PM +0100, Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 12:24:26PM -0300, Alvaro Herrera wrote:
Martijn van Oosterhout wrote:
On Wed, Nov 28, 2007 at 11:57:35AM -0300, Alvaro Herrera wrote:
Can we do something like this to
On Thu, Nov 29, 2007 at 09:43:30AM -0300, Alvaro Herrera wrote:
Magnus Hagander wrote:
On Thu, Nov 29, 2007 at 09:09:47AM -0300, Alvaro Herrera wrote:
Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 05:20:46PM +0100, Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 12:24:26PM -0300,
Magnus Hagander wrote:
On Thu, Nov 29, 2007 at 09:09:47AM -0300, Alvaro Herrera wrote:
Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 05:20:46PM +0100, Magnus Hagander wrote:
On Wed, Nov 28, 2007 at 12:24:26PM -0300, Alvaro Herrera wrote:
Martijn van Oosterhout wrote:
On Wed,
Hi,
The PostgreSQL 8.3 documentation[1] says this about lo_export and
lo_import paths and servers:
Import:
Note that the file is read by the client interface library, not by
the server; so it must exist in the client file system and be
readable by the client application.
Export:
Jorgen Austvik - Sun Norway wrote:
Problem between keyboard and chair, in doc, libpq, psql or elsewhere?
Sorry, the psql documentation is clear on this:
\lo_export
Note that this is subtly different from the server function lo_export,
which acts with the permissions of the user that the
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
I'm a bit puzzled myself why this affects SELECT FOR UPDATE/SHARE but not
straight UPDATES and DELETES.
In straight UPDATE/DELETE we have enough structure in the query to know
how to associate each tuple returned to
Magnus Hagander wrote:
On Thu, Nov 29, 2007 at 09:43:30AM -0300, Alvaro Herrera wrote:
Magnus Hagander wrote:
Maybe. I'm concerned we might end up logging a whole lot more, for cases
where it's not an actual error. For example, a file that doesn't exist
doesn't necessarily mean it's
Apologies, if some of you receive duplicates of this email. I am not
subscribed to -www, so sending this to - hackers again.
Hi,
On Wed, 2007-11-28 at 11:44 +0530, Pavan Deolasee wrote:
Nikhil S
Nikhil is from India, EnterpriseDB.
What is his surname? I think we
Hi all,
I'm trying to write a trigger that converts integer to bytea.
My schema is like this:
Create table xx (
id int,
...
data bytea);
the first 3 bytes of data are the binary representation of id
(id is extracted from data by the application)
I can occur that id change in that case
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
+* Fill in just enough information to set up this perl
+* function in the safe container and call it.
+* For some reason not entirely clear, it prevents
errors
Hi Gregory
On Thu, 29 Nov 2007, Gregory Stark wrote:
Date: Thu, 29 Nov 2007 14:34:57 +
From: Gregory Stark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: pgsql-hackers list pgsql-hackers@postgresql.org
Subject: Re: convert int to bytea
[EMAIL PROTECTED] writes:
select 124::bytea
[EMAIL PROTECTED] writes:
select 124::bytea doesn't work
Is there an other way? (preferabily simple :)
This kind of question would be more appropriate on pgsql-general.
What do you want the resulting bytea to look like?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Alvaro Herrera [EMAIL PROTECTED] writes:
Magnus Hagander wrote:
Maybe. I'm concerned we might end up logging a whole lot more, for cases
where it's not an actual error.
I'm very concerned about that too, and think that DEBUG5 is just fine.
Hmm, I just noticed a bug in those fprintf calls --
[EMAIL PROTECTED] writes:
Hmm, isn't 4h22m a LONG time for it even with clobbered cache?
All my tests so far have last less than 2h..
I'm sure that yesterday' LookupOpclassInfo change would have made
it even more mind-bogglingly slow than before...
regards, tom lane
On 11/29/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, 29 Nov 2007, Gregory Stark wrote:
What do you want the resulting bytea to look like?
example : id = 9 , bytea = '\000\000\011' IIRC
What do you expect to happen when server and client are differently-endian?
-Doug
Does it matter if you have written an explicit cast for int to bytea?
On Nov 29, 2007 9:00 PM, Douglas McNaught [EMAIL PROTECTED] wrote:
On 11/29/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, 29 Nov 2007, Gregory Stark wrote:
What do you want the resulting bytea to look like?
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Magnus Hagander wrote:
Maybe. I'm concerned we might end up logging a whole lot more, for cases
where it's not an actual error.
I'm very concerned about that too, and think that DEBUG5 is just fine.
Well, the analysis was already
I wanted to give everyone an overview of where we are for 8.3. We have
addressed almost every major issue for 8.3 but we are getting a steady
stream of minor cleanups. These cleanups are vital to keep the quality
of Postgres at a high level. It allows us to make major changes in
every release
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm very concerned about that too, and think that DEBUG5 is just fine.
Well, the analysis was already done which says this shouldn't be a problem.
That analysis is full of holes --- FileRead and FileWrite for starters.
Hi,
please don't top post to someone who didn't used this convention
in answering you. It's impolite. I edited the mail a bit to return sanity.
On Nov 29, 2007 9:00 PM, Douglas McNaught [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On 11/29/07, [EMAIL PROTECTED] mailto:[EMAIL
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm very concerned about that too, and think that DEBUG5 is just fine.
Well, the analysis was already done which says this shouldn't be a problem.
That analysis is full of holes --- FileRead and FileWrite for
On Nov 29, 2007 9:35 PM, Zoltan Boszormenyi [EMAIL PROTECTED] wrote:
Hi,
please don't top post to someone who didn't used this convention
in answering you. It's impolite. I edited the mail a bit to return sanity.
On Nov 29, 2007 9:00 PM, Douglas McNaught [EMAIL PROTECTED]
mailto:[EMAIL
Usama Dar wrote:
2) i know what a byte order is , i just thought your interface i.e.
libpq would convert it to the local byte order.
You haven't thought this through. Data traveling over libpq is still
text, not binary, in most cases, so byte order is irrelevant at that
time. The
On Wed, Nov 21, 2007 at 03:33:53PM -0500, Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
On Mon, 2007-11-19 at 02:50 -0700, Kris Jurka wrote:
Can we backport this fix? I'm trying to setup a new windows build
environment and this is currently halting my progress for back
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
That analysis is full of holes --- FileRead and FileWrite for starters.
I already did. The case where they retry do not call _dosmaperr.
What's retry got to do with it? What's displeasing me is the idea of
LOG messages showing up
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
That analysis is full of holes --- FileRead and FileWrite for starters.
I already did. The case where they retry do not call _dosmaperr.
What's retry got to do with it? What's displeasing me is the idea of
LOG
Hi folks,
The patch is coming along nicely now. I do have a couple of questions
about the implementation in transformArrayExpr though.
1) How should we determine whether the array is multidimensional if we
know the type in advance?
Currently, transformArrayExpr uses the results of its
On Fri, Nov 30, 2007 at 06:13:20AM +1100, Brendan Jurd wrote:
Hi folks,
The patch is coming along nicely now. I do have a couple of questions
about the implementation in transformArrayExpr though.
Awesome.
1) How should we determine whether the array is multidimensional if we
know the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Nov 2007 12:00:51 -0800
Andrew Hammond [EMAIL PROTECTED] wrote:
software. I doubt there are any plans to trim the 7.3 branch from CVS
and I imagine that the community will be happy to work with anyone
Considering we still have
On Nov 29, 2007 11:11 AM, Ron Mayer [EMAIL PROTECTED] wrote:
Robert Treat wrote:
On Tuesday 27 November 2007 15:07, Simon Riggs wrote:
On Tue, 2007-11-27 at 14:02 -0500, Tom Lane wrote:
There has been some discussion of making a project policy of dropping
support for old releases after
I was able to reproduce the problem complained of here
http://archives.postgresql.org/pgsql-bugs/2007-11/msg00322.php
with this function:
create or replace function foo() returns int as $$
declare r int;
begin
drop table if exists temptable cascade;
create temp table temptable as select *
Alvaro Herrera [EMAIL PROTECTED] writes:
I think a reasonable compromise is to turn the ereport() in _dosmaperr
to DEBUG1 instead. That way it won't clutter any log by default, and in
the cases where we're actually interested in tracking the problematic
situation, we don't need to get huge
Magnus Hagander [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm still not convinced what you think the problematic situation is.
I believe Alvaros point is that several different GetLastError codes map
to the same errno code, making it impossible to see the difference
between those errors.
Martijn van Oosterhout [EMAIL PROTECTED] writes:
1) How should we determine whether the array is multidimensional if we
know the type in advance?
Well, given the array should be regular you should be able to just look
at the first element, if it's a array look at it's first element, etc
to
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I think a reasonable compromise is to turn the ereport() in _dosmaperr
to DEBUG1 instead. That way it won't clutter any log by default, and in
the cases where we're actually interested in tracking the problematic
situation, we don't
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm still not convinced what you think the problematic situation is.
I believe Alvaros point is that several different GetLastError codes map
to the same errno code, making it impossible to see the difference
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
(2) Do we have any live cases where we must know this?
Yes. This thread shows the problem:
http://archives.postgresql.org/pgsql-es-ayuda/2007-11/msg00354.php
Basically he is getting this error:
2007-11-16 14:54:16 ERROR: could not
On Thu, 2007-11-29 at 11:26 -0500, Bruce Momjian wrote:
I expect these cleanups to continue for at least another week or two.
Once they slow we will schedule RC1.
So are there no plans for an additional beta? Given the recent addition
of changes like
On Thu, 29 Nov 2007, Andrew Dunstan wrote:
The version I tested against is 5.8.8 - the latest stable release. The
5.8 series started in 2003 from what I can see - if anyone has a
sufficiently old system that they can test on 5.6.2 that will be useful.
I've got a 5.6.1 perl here, but it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Nov 2007 14:01:11 -0800
Neil Conway [EMAIL PROTECTED] wrote:
On Thu, 2007-11-29 at 11:26 -0500, Bruce Momjian wrote:
I expect these cleanups to continue for at least another week or
two. Once they slow we will schedule RC1.
So are
Neil Conway [EMAIL PROTECTED] writes:
So are there no plans for an additional beta?
Yes, there are, but not till we do something about
http://archives.postgresql.org/pgsql-hackers/2007-11/msg01302.php
regards, tom lane
---(end of
Robert Treat wrote:
On Tuesday 27 November 2007 15:07, Simon Riggs wrote:
On Tue, 2007-11-27 at 14:02 -0500, Tom Lane wrote:
There has been some discussion of making a project policy of dropping
support for old releases after five years. Should we consider formally
instituting that?
...
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
(2) Do we have any live cases where we must know this?
Yes. This thread shows the problem:
http://archives.postgresql.org/pgsql-es-ayuda/2007-11/msg00354.php
Basically he is getting this error:
2007-11-16
Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
(2) Do we have any live cases where we must know this?
Yes. This thread shows the problem:
http://archives.postgresql.org/pgsql-es-ayuda/2007-11/msg00354.php
Basically he is getting this error:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
Well, since EINVAL is the default result from _dosmaperr, and none of
the cases it represents are expected, why don't we just remove all of
the explicit mappings to EINVAL from doserrors[]?
Well, the problematic routine is not already
Andreas 'ads' Scherbaum [EMAIL PROTECTED] writes:
i would also like to test another Beta, if we do something about this
problem:
http://archives.postgresql.org/pgsql-hackers/2007-11/msg00960.php
That's already done, it would be in the next beta. You could check out a copy
from CVS HEAD if
Tom Lane [EMAIL PROTECTED] writes:
One fairly simple answer is to insert a CCI call at the start of
RevalidateCachedPlan. I dislike that solution, at least by itself,
on two grounds:
* A patch of that form would approximately double the number of CCI
calls involved in executing a plpgsql
Hello,
On Thu, 29 Nov 2007 17:21:09 -0500 Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
So are there no plans for an additional beta?
Yes, there are, but not till we do something about
http://archives.postgresql.org/pgsql-hackers/2007-11/msg01302.php
i would also like to test
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Nov 2007 14:01:11 -0800
Neil Conway [EMAIL PROTECTED] wrote:
On Thu, 2007-11-29 at 11:26 -0500, Bruce Momjian wrote:
I expect these cleanups to continue for at least another week or
two. Once they slow
On Nov 30, 2007 11:10 AM, Andreas 'ads' Scherbaum [EMAIL PROTECTED] wrote:
i would also like to test another Beta, if we do something about this
problem:
http://archives.postgresql.org/pgsql-hackers/2007-11/msg00960.php
Hi Andreas,
Tom's already committed the quote_literal(anyelement)
On Fri, 30 Nov 2007 11:26:35 +1100 Brendan Jurd wrote:
On Nov 30, 2007 11:10 AM, Andreas 'ads' Scherbaum [EMAIL PROTECTED] wrote:
i would also like to test another Beta, if we do something about this
problem:
http://archives.postgresql.org/pgsql-hackers/2007-11/msg00960.php
Hi
Gregory Stark [EMAIL PROTECTED] writes:
Wait, shouldn't it be sufficient to do a CCI only in the if (!plan) case?
No. The problem is that if you don't do the CCI then you don't get the
invalidation events that might-or-might-not be pending in the inval
queue. So testing for whether the plan is
Few proposals
- Can we say smoothed rather than distributed checkpoints?
Smoothed checkpoints greatly reduce checkpoint I/O spikes
- Heap-Only Tuples (HOT) accelerate space reuse for UPDATEs
change to
Heap-Only Tuples (HOT) improve performance of frequent UPDATEs
I also notice that two
Hi,
The following bug has been logged online:
Bug reference: 3774
Logged by: guillaume (ioguix) de Rorthais
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3 beta3
Operating system: mac os x 10.4.10
Description:create table like including index
63 matches
Mail list logo
