Jan Wieck wrote:
I committed the first part of the background writer process. We had a
consensus on attempting to avoid write() calls from regular backends,
but did no come to any conclusions what to do to force the kernel to
actually do some IO.
Consequently, this patch is a separate process
Joshua D. Drake wrote:
Is there some way to remove this piece of sh^H^Hlegacy from the
configure script? Does anybody actually use info?
All of GNU.
Additionally it is very good resource when you use Konqueror to browse it as html..
Shridhar
---(end of broadcast)
strk <[EMAIL PROTECTED]> writes:
> Testing postgis support in PG7.4 (2003-11-11)
> I've encountered to this problem:
> ERROR: could not identify an ordering operator for type geometry
> Previous PG versions does not show this problem.
> Any hint on what might be missing ?
A default btree
Josh Berkus <[EMAIL PROTECTED]> writes:
> Peter wrote:
>> Also note that most major number
>> changes in the past weren't because the features were cool, but because
>> the project has moved to a new phase. I don't see any such move
>> happening.
> Now that is interesting. I missed that. Can y
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> COMMENT ON AGGREGATE newcnt (any) IS 'an any agg comment';
> ERROR: syntax error at or near "any" at character 30
ANY is a reserved word. To reference the pseudotype named "any",
you need quotes:
COMMENT ON AGGREGATE newcnt ("any") IS
Don Sceifers wrote:
> My company is fairly new at Postgresql, but we have hit a problem, where
> we modify a table using ALTER, and our stored procedures stop working. We
> have a grasp as to why this happens, but I was wondering if this v7.4
> upgrade fixes this issue?
This is a known issue. The
Why should ALTER COLUMN change the column number, i.e. position?
Because it creates a NEW column.
It may be that programmers should not rely on this, but it happens,
and in very
large projects. If we can avoid unexpected side-affects like moving the
columns position, then I think we should.
T
Marcel Kornacker did implement concurrency for GiST - I confirmed as
much with Joe Hellerstein (his advisor). I know there's a paper he
wrote with C.Mohan on it. I don't know which version his
implementation was for.
The 7.4 GiST docs have a link to Kornacker's thesis that details how to
implement
Andrew Dunstan writes:
> Essentially what I have is something like this pseudocode:
>
> cvs update
Be sure check past branches as well.
> check if there really was an update and if not exit
OK.
> configure; get config.log
Ideally, you'd try all possible option combinations for configure
Hannu Krosing wrote:
To put it differently: a ALTER COLUMN command may never-ever change the
identifier of the column, i.e. attrelid/attnum.
to be even more restirictive: ALTER COLUMN may never-ever change the
type of the column, as this too may break some apps. Nah!
Yeah, and the data sh
On Wed, 2003-11-19 at 17:02, Robert Treat wrote:
> I don't think *we* thought it was a hot button issue.. at least I
> certainly didn't when I initially responded.
Well, I hear that. I think this little exercise though, is good for the
community as a whole. It's a concern I think lots of business
I don't think *we* thought it was a hot button issue.. at least I
certainly didn't when I initially responded. There is no need for you to
apologize, in fact, I'll apologize for the list, we sometimes get a
little heated on -hackers. Hopefully you've not been to startled by this
outburst :-)
Rober
Andreas Pflug kirjutas K, 19.11.2003 kell 20:45:
> Dave Cramer wrote:
> >>Why should ALTER COLUMN change the column number, i.e. position?
> >
> >Rod's current proposed patch does that if you do an alter column alter
> >type. This is an artifact of the underlying mechanism. (ren old col, add
> >new
Is there some way to remove this piece of sh^H^Hlegacy from the
configure script? Does anybody actually use info?
All of GNU.
Cheers,
D
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-22
All,
I sincerely apologize for possibly starting a flame war, I wasn't aware
this might be a hot-button issue. Hopefully some good will come of it
none-the-less, like others who come after me might see the reasons our
db application developers want this type of "go to" support.
I would also si
Kind people,
Is there some magic I can use to keep the following from happening in
the when I build from the .spec file? I'm starting with the
Postgresql 7.3.4 spec file, version bumped, patches removed.
configure: error: unrecognized option: --infodir=/usr/share/info
Is there some way to remov
Hello
Tell me if I am significantly wrong but Command Prompt PostgreSQL is
nothing more than "Open Source PostgreSQL" including some application
server stuff, some propriertary PL/Perl || PL/PHP and not much more.
Ahh no.
First our PL/Perl and PL/PHP is not propiertary in any way. It is open
On Wed, 2003-11-19 at 10:47, Sailesh Krishnamurthy wrote:
> > "Mike" == Mike Mascari <[EMAIL PROTECTED]> writes:
>
> Mike> Robert Treat wrote:
>
> >> While some form of bitmapped indexing would be cool, other ideas might
> >> be to implement different buffer manager strategies. I
Does with(isStrict) still work ?
If not when did postgres drop its support ?
TIA
--strk;
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Hello,
I think what the person is looking for is:
COMPANY PostgreSQL for Red Hat Enterprise 3.0.
They probably have some commercial mandate that says that they have
to have a commercial company backing the product itself. This doesn't
work for most PostgreSQL companies because they back the "
Nigel J. Andrews wrote:
On Wed, 19 Nov 2003, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Wed, 19 Nov 2003, Michael Meskes wrote:
On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
I've been looking all over but I can't seem to see a company that is
providing *up-to-date* postg
On Wed, 2003-11-19 at 11:17, Don Sceifers wrote:
> My company is fairly new at Postgresql, but we have hit a problem, where
> we modify a table using ALTER, and our stored procedures stop working. We
> have a grasp as to why this happens, but I was wondering if this v7.4
> upgrade fixes this issue?
On Mon, Nov 17, 2003 at 02:48:08PM -0500, Rod Taylor wrote:
> The PostgreSQL group has recently had a patch submitted with a snippet
> of code from FreeBSDs src/bin/mkdir/mkdir.c.
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/bin/mkdir/mkdir.c?annotate=1.27
>
> Is this intentionally under the 4 c
I found the uses of int2, int16 and other similiar types misleading
in PostgreSQL's source code. Sometime it is difficult to figure out
which should be prefered.
Maybe int2, int4, and int8 refer to database types, while int16, int32
and int64 refer to C data types. If this is the convention, maint
On Tue, Nov 18, 2003 at 12:18:51PM -0500, Andrew Sullivan wrote:
> On Tue, Nov 18, 2003 at 08:39:29AM -0800, ow wrote:
> >
> > Have *never* seen ppl running Oracle or Sybase on Windows.
>
> I _have_ certainly seen plenty of people running Oracle on Windows.
> They weren't necessarily happy, of
Hi
> You
> probably aren't faced with this issue as much in Germany, but it
happens
> often to us folks in the US & Canada.
About half of the mails that I get are Cygwin-Windows related. So I
consider it of great interest in Germany.
Regards
Conni
---(end of broadcast)-
My company is fairly new at Postgresql, but we have hit a problem, where
we modify a table using ALTER, and our stored procedures stop working. We
have a grasp as to why this happens, but I was wondering if this v7.4
upgrade fixes this issue?
Don Sceifers
Harvest Info
<>
-
> > > Least interesting to many user perhaps, but lost of them
> > seen to think
> > > that it's important for expanding our userbase:
> > > http://www.postgresql.org/survey.php?View=1&SurveyID=9
> > That does not say that better entertainment will attract new
> > viewers, just that the existing v
On Mon, 17 Nov 2003 14:48:08 -0500
Rod Taylor <[EMAIL PROTECTED]> wrote:
> The PostgreSQL group has recently had a patch submitted with a snippet
> of code from FreeBSDs src/bin/mkdir/mkdir.c.
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/bin/mkdir/mkdir.c?annotate=1.27
This appears to be an ori
Peter Eisentraut wrote:
The Samba build daemon suite is pretty good. We have a couple of those
hosts in our office in fact. (I think they're building PostgreSQL
regularly as well.) A tip: You might find that adopting the source code
of the Samba suite to PostgreSQL is harder than writing a new
On Wed, 2003-11-19 at 12:16, Sailesh Krishnamurthy wrote:
> > "Robert" == Robert Treat <[EMAIL PROTECTED]> writes:
>
> Robert> allowing indexes for searching nulls, or adding
> Robert> concurrency to GIST, or allowing non btree indexes to
>
> Oh this has come up before on -hackers and
> Where have you found this?
>
> I've been looking for that but have not found it. I run a rh9 system, do
> you have something newer? Maybe I have just not looked in the right place
> in the documentation.
Glibc 2.3 implements both reentrant and a thread local locale APIs.
The reentrant API pr
On Wed, 19 Nov 2003, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Wed, 19 Nov 2003, Michael Meskes wrote:
> >
> > > On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
> > > > I've been looking all over but I can't seem to see a company that is
> > > > providing *up-to-date* p
Marc G. Fournier wrote:
> On Wed, 19 Nov 2003, Michael Meskes wrote:
>
> > On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
> > > I've been looking all over but I can't seem to see a company that is
> > > providing *up-to-date* postgresql support and provides their own
> > > supporte
On Wed, 2003-11-19 at 11:31, Marc G. Fournier wrote:
> On Wed, 19 Nov 2003, Michael Meskes wrote:
>
> > On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
> > > I've been looking all over but I can't seem to see a company that is
> > > providing *up-to-date* postgresql support and prov
Dave Cramer wrote:
Andreas,
On Wed, 2003-11-19 at 13:07, Andreas Pflug wrote:
Dave Cramer wrote:
Andreas,
The point of this is to maintain the column position. I don't think that
an alter of a column type should move the column position.
Why should ALTER COLUMN change the column
Andrew Dunstan writes:
> Maybe it wouldn't be of great value to PostgreSQL. And maybe it would. I
> have an open mind about it. I don't think incompleteness is an argument
> against it, though.
If you want to do it, by all means go for it. I'm sure it would give
everyone a fuzzy feeling to see t
Andreas,
On Wed, 2003-11-19 at 13:07, Andreas Pflug wrote:
> Dave Cramer wrote:
>
> >Andreas,
> >
> >The point of this is to maintain the column position. I don't think that
> >an alter of a column type should move the column position.
> >
> Why should ALTER COLUMN change the column number, i.e.
Dave Cramer wrote:
Andreas,
The point of this is to maintain the column position. I don't think that
an alter of a column type should move the column position.
Why should ALTER COLUMN change the column number, i.e. position?
It may be that programmers should not rely on this, but it happens, and
andrew wrote:
> Ok, seriously weird. This is apparently from the pg_type relation and
> looks just fine on my installation.
>
> Have you tried "make distclean; cvs update; configure; make check" ?
Tried now: 4 of 93 tests failed.
.. initdb does not fault though ;)
It seems that the build system
Lamar Owen wrote:
> On Wednesday 19 November 2003 12:02 pm, Peter Eisentraut wrote:
> > Lamar Owen writes:
> > > And he is getting paid to do it, unlike me.
> >
> > That's news to me. :-)
>
> Reinhard Max is getting paid to do it, not you. Bad english on my part.
As I remember, Peter's company,
Andreas,
The point of this is to maintain the column position. I don't think that
an alter of a column type should move the column position. It may be
that programmers should not rely on this, but it happens, and in very
large projects. If we can avoid unexpected side-affects like moving the
colum
TODO updated:
* -Use background process to write dirty shared buffers to disk
---
Jan Wieck wrote:
> I committed the first part of the background writer process. We had a
> consensus on attempting to avoid write()
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
On Wed, 19 Nov 2003, Michael Meskes wrote:
> On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
> > I've been looking all over but I can't seem to see a company that is
> > providing *up-to-date* postgresql support and provides their own
> > supported binaries. Am I barking up the wron
Lamar Owen writes:
> And he is getting paid to do it, unlike me.
That's news to me. :-)
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Christopher Kings-Lynne wrote:
Will adding the logical attribute number break all of the external
tools? pg_dump, etc are all dependent on attnum now?
Would it be possible to keep the meaning of attnum the same externally
and add another column internally to represent the physical number?
Inter
On Wednesday 19 November 2003 12:02 pm, Peter Eisentraut wrote:
> Lamar Owen writes:
> > And he is getting paid to do it, unlike me.
>
> That's news to me. :-)
Reinhard Max is getting paid to do it, not you. Bad english on my part.
--
Lamar Owen
Director of Information Technology
Pisgah Astronom
> "Robert" == Robert Treat <[EMAIL PROTECTED]> writes:
Robert> allowing indexes for searching nulls, or adding
Robert> concurrency to GIST, or allowing non btree indexes to
Oh this has come up before on -hackers and I've been meaning to chime
in.
Marcel Kornacker did implement concu
Shridhar,
> However I do not agree with this logic entirely. It pegs the next vacuum
> w.r.t current table size which is not always a good thing.
No, I think the logic's fine, it's the numbers which are wrong. We want to
vacuum when updates reach between 5% and 15% of total rows. NOT when
u
Peter Eisentraut wrote:
Andrew Dunstan writes:
"Useful" is probably subjective. That list would at least be a good
place to start, though. What combinations of variables do you think we
would need?
First of all, I don't necessarily think that a large list of CPU/operation
system combinati
I committed the first part of the background writer process. We had a
consensus on attempting to avoid write() calls from regular backends,
but did no come to any conclusions what to do to force the kernel to
actually do some IO.
Consequently, this patch is a separate process launched by postma
Michael Meskes wrote:
> On Wed, Nov 19, 2003 at 11:02:59AM +, Lee Kindness wrote:
> > Hi, please apply patch below to correct the EXEC SQL CREATE SCHEMA
> > construct in ECPG. Currently (versions 7.3.x, 7.4) the preprocessor
> > emmits "create scheme" in error, rather than "create schema".
>
>
Robert Treat wrote:
If by up to date you mean 7.4, your probably going to have to wait, but
I believe that Command Prompt, dbExperts, Red Hat, and SRA all have some
type of binary based support available.
Don't forget to mention us ... ;).
Cheers,
Hans
--
Cybertec Geschwinde u Schoenig
Ludo-H
strk wrote:
Running initdb:
creating template1 database in /pgroot-cvs/data/base/1 ... child process was terminated by signal 11
It is working fine for me (RH9). Can you provide more details? Platform?
How you are calling initdb?
cheers
andrew
---(end of broadcast)
On Monday 17 November 2003 05:28 pm, Daniele Orlandi wrote:
> Yesterday I was a bit worried... I switched to SuSE just 2 weeks ago...
> my newly installed databse server was waitinI thought that I would have
> to wait so much to have RPMs for SuSE and today I see v7.4 compiled for
> many flavors of
On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
> I've been looking all over but I can't seem to see a company that is
> providing *up-to-date* postgresql support and provides their own
> supported binaries. Am I barking up the wrong tree entirely here?
Why do you insist on "their o
> "Mike" == Mike Mascari <[EMAIL PROTECTED]> writes:
Mike> Robert Treat wrote:
>> While some form of bitmapped indexing would be cool, other ideas might
>> be to implement different buffer manager strategies. I was impressed by
>> how quickly Jan was able to implement ARC over
> >>1. Open WAL files with O_SYNC|O_DIRECT or O_SYNC(Not sure if
> > Without grouping WAL writes that does not fly. Iff however such grouping
> > is implemented that should deliver optimal performance. I don't think flushing
> > WAL to the OS early (before a tx commits) is necessary, since writi
Andrew Dunstan writes:
> "Useful" is probably subjective. That list would at least be a good
> place to start, though. What combinations of variables do you think we
> would need?
First of all, I don't necessarily think that a large list of CPU/operation
system combinations is going to help much.
On Tue, 2003-11-18 at 17:31, Sailesh Krishnamurthy wrote:
> > "Mike" == Mike Mascari <[EMAIL PROTECTED]> writes:
> Mike> How about extra credit for PITR?
>
> One step at a time :-)
>
> Actually a big problem is figuring out new pieces for the
> projects. Most of the items in the TODO list
On Wed, Nov 19, 2003 at 11:02:59AM +, Lee Kindness wrote:
> Hi, please apply patch below to correct the EXEC SQL CREATE SCHEMA
> construct in ECPG. Currently (versions 7.3.x, 7.4) the preprocessor
> emmits "create scheme" in error, rather than "create schema".
Thanks. Applied to HEAD and 7.4.
Marc G. Fournier wrote:
On Tue, 18 Nov 2003, Peter Eisentraut wrote:
The time from release 7.3 to release 7.4 was 355 days, an all-time high.
We really need to shorten that. We already have a number of significant
improvements in 7.5 now, and several good ones coming up in the next few
weeks. W
Josh Berkus wrote:
Shridhar,
I was looking at the -V/-v and -A/-a settings in pgavd, and really don't
understand how the calculation works. According to the readme, if I set -v
to 1000 and -V to 2 (the defaults) for a table with 10,000 rows, pgavd would
only vacuum after 21,000 rows had been
If by up to date you mean 7.4, your probably going to have to wait, but
I believe that Command Prompt, dbExperts, Red Hat, and SRA all have some
type of binary based support available.
Robert Treat
On Tue, 2003-11-18 at 17:19, Austin Gonyou wrote:
> I've been looking all over but I can't seem to
Robert Treat wrote:
> On Tue, 2003-11-18 at 17:31, Sailesh Krishnamurthy wrote:
>>
>>One step at a time :-)
>>
>>Actually a big problem is figuring out new pieces for the
>>projects. Most of the items in the TODO list are way too much for a
>>class project - we gave 'em 3 weeks to make the Hash Gr
Peter Eisentraut wrote:
Andrew Dunstan writes:
If there's general interest I'll try to cook something up. (This kind of
stuff is right up my alley). I'd prefer some automated display of
results, though. A simple CGI script should be all that's required for
that.
The real problem will be
Running initdb:
creating template1 database in /pgroot-cvs/data/base/1 ... child process was
terminated by signal 11
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatype
Hi, please apply patch below to correct the EXEC SQL CREATE SCHEMA
construct in ECPG. Currently (versions 7.3.x, 7.4) the preprocessor
emmits "create scheme" in error, rather than "create schema".
A workaround also exists for those who require it (but I guess no-one
apart from me does since it's w
> "Greg" == Greg Stark <[EMAIL PROTECTED]> writes:
Greg> I think you're talking about situations like "where x = ? or
Greg> y = ?" or "where x = ? and y = ?"
Greg> When both `x' and `y' are indexed. It's possible to do the
Greg> index lookup, gather a list of tid pointers in
Jean-Michel POURE wrote:
OK, now, some of us will complain that Win32 is not needed at a time when the
Debian Synaptic graphical installer gives access to 13.748 packages. Win32
sounds like an "old Atari game station". Agreed. On the long-run, everyone
will leave Win32, even my grand-mother.
Wel
Testing postgis support in PG7.4 (2003-11-11)
I've encountered to this problem:
ERROR: could not identify an ordering operator for type geometry
HINT: Use an explicit ordering operator or modify the query.
Whenever I issue one of these commands:
gis=# select the_geom fr
Le Mardi 18 Novembre 2003 20:22, ow a écrit :
> Not really. I simply think there are more pressing issues than win32 port.
Dear friends,
Porting to Win32 can multiply:
- direct users (i.e. developers) by a factor of two or three,
- indirect users by a larger factor, provided that major projects i
Andrew Dunstan writes:
> If there's general interest I'll try to cook something up. (This kind of
> stuff is right up my alley). I'd prefer some automated display of
> results, though. A simple CGI script should be all that's required for
> that.
The real problem will be to find enough machines s
74 matches
Mail list logo
