"Thomas Hallgren" <[EMAIL PROTECTED]> writes:
>> ... Furthermore, AFAICT shl_load()
>> requires an exact path spec for the initial shared library; it won't
>> do a path search for that, only for dependencies.)
>>
> Here's an excerpt from the HPUX manual pages on dlopen(3C).
HPUX which? There is
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> This only applies to dev versions, as the library version is bumped each
> release, I believe.
Bumping the minor version number is part of Bruce's standard per-release
checklist. However, it seems to me that there are some popular
platforms (eg Linux)
Hi all
How can i read transactions from "write ahead log " pg_xlog ?
It is possible ?
regards
S.W
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
- Original Message -
From: <[EMAIL PROTECTED]>
Sent: June 08, 2004 2:27 PM
> Date: Tue, 8 Jun 2004 13:03:22 -0300 (ADT)
> From: "Marc G. Fournier" <[EMAIL PROTECTED]>
> Subject: Releasing 7.4.3 ...
> Next Monday, we're going to put out a 7.4.3 release, incorporating all the
> little pat
Hi Everyone,
I'm not sure of the detail behind winsup/cygwin/localtime.cc, but there are
problems with how Cygwin handles dates and times on Windows.
See http://www.cygwin.com/ml/cygwin/2003-07/msg01016.html.
If there is any relevance, I think it is imperative that the Win32 version
of PostgreSQ
Was this another of those darn regurgitated-from-February messages?
I'm about ready to go out and acquire missile targeting coordinates
for pcbuddy.com ...
Hmmm, maybe - I don't have the email any more though, as I deleted it :(
I get regurgitated emails all the time - it can be quite confusing...
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Yep, Tom fixed it good.
Was this another of those darn regurgitated-from-February messages?
I'm about ready to go out and acquire missile targeting coordinates
for pcbuddy.com ...
regards, tom lane
I'm nearly ready to commit a patch that adds support for INSERT and
UPDATE assignments to individual fields of composite columns,
along the lines of
UPDATE mytab SET complex_col.r = (complex_col).r + 1 WHERE ...;
INSERT INTO mytab (complex_col.r, complex_col.i) VALUES(1.1, 2.2);
This turned out
Dennis Bjorklund wrote:
> When I try to commit to cvs it gets stuck and outputs this messages every
> 30:th second:
>
> cvs server: [11:11:28] waiting for ishii's lock in
> /cvsroot/pgsql-server/src/bin/pg_controldata/po
Fixed. Thanks.
--
Bruce Momjian| http://candl
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Email interface: it should not be beyond the wit of man to provide some level
> of email interface to any reasonable bug tracking system. Whether or not it is
> worth doing depends on the demand. Two obvious places for it would be 1) to
> allow initial
Yep, Tom fixed it good.
Bruce Momjian wrote:
I can confirm that current CVS handles this OK.
---
Christopher Kings-Lynne wrote:
I had a suspicion and it was confirmed:
test=# create table oidtest (a int4, unique(oid));
NOTICE:
I can confirm that current CVS handles this OK.
---
Christopher Kings-Lynne wrote:
> I had a suspicion and it was confirmed:
>
> test=# create table oidtest (a int4, unique(oid));
> NOTICE: CREATE TABLE / UNIQUE will creat
[EMAIL PROTECTED] wrote:
The best phrasing would be "the accumulating overhead of deletes and
updates."
Yes.
Are you using 7.3?
I am asking because in 7.3 high update / delete tables could suffer
(index and toast) bloat that was untamable via (lazy) VACUUM and FSM.
I believe this is fixed in 7.
On Fri, 27 Feb 2004, Josh Berkus wrote:
Paul,
Your main concern about RT isn't true, at least here at my office. I
installed RT, with no prior experience with any OSS tracker, back in
October, and it worked on PostgreSQL the first time. (PostgreSQL support was
one of the main reasons I chose it to
"scott.marlowe" <[EMAIL PROTECTED]> writes:
> On Fri, 27 Feb 2004, Tom Lane wrote:
>> In my mind, one of the main benefits of this work will be that we'll be
>> able to get *rid* of the initlocation stuff. It's a crock.
> OK, that's fine, but I keep thinking that a superuser should have to
> cre
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dann Corbit
> Sent: Tuesday, February 24, 2004 4:21 PM
> To: Peter Eisentraut; PostgreSQL-development
> Subject: Re: [HACKERS] Is indexing broken for bigint columns?
>
>
> > -Original Message-
Alvaro Herrera wrote:
> On Tue, Jun 08, 2004 at 12:44:22PM -0400, Andrew Dunstan wrote:
>
> > This only applies to dev versions, as the library version is bumped each
> > release, I believe.
>
> Actually, the library version is not bumped each release --- in fact,
> there has been at least one t
On Tue, Jun 08, 2004 at 02:03:05PM -0400, Andrew Dunstan wrote:
> Alvaro Herrera wrote:
>
> >I do that, and I have rpath enabled (that's the default, isn't it?) but
> >my solution is to have no version in normal directories (i.e. they are
> >all installed in $HOME/pgsql/some-version-number/ )
>
>
>
>
> [EMAIL PROTECTED] wrote:
>
>>I've been down several roads about how to handle data that has to change
>>on a very frequent and rapid manner.
>>
>>Think about summary tables, WEB session tables, etc. As great as MVCC is
>>for the vast majority of uses. The overhead of updates and deletes can
>
[EMAIL PROTECTED] wrote:
I've been down several roads about how to handle data that has to change
on a very frequent and rapid manner.
Think about summary tables, WEB session tables, etc. As great as MVCC is
for the vast majority of uses. The overhead of updates and deletes can
kill a project that
I've been down several roads about how to handle data that has to change
on a very frequent and rapid manner.
Think about summary tables, WEB session tables, etc. As great as MVCC is
for the vast majority of uses. The overhead of updates and deletes can
kill a project that needs to constantly upda
Magnus Hagander wrote:
Specifically about the logs, I still think there is a lot of value to
being able to read the logs remotely even if you can't restart
postmaster.
Since I believe that retrieving the logs easily without server file
access is a feature that's welcomed by many users, here's my p
> The variations among platforms are great enough that I don't think you
> can make such an assertion.
>
> (To take one example, HPUX does have a variable like this --- they call
> it SHLIB_PATH --- but it *is not used* unless a flag enabling it was
> provided when the shlib was linked, and I thin
Alvaro Herrera wrote:
IOW it's purely a developer's trap (which has caught me in the past).
If you build and install multiple dev versions you should think about
disabling rpath.
I do that, and I have rpath enabled (that's the default, isn't it?) but
my solution is to have no version in normal
"Andrew Dunstan" <[EMAIL PROTECTED]> wrote:
> And many people just hate playing games with LD_LIBRARY_PATH, and even
> more hate apps that do it.
>
The current design forces me and anyone else who wants a module that depends
on shared libraries to play these games. My suggestion is that we hide thi
"Thomas Hallgren" <[EMAIL PROTECTED]> writes:
> The LD_LIBRARY_PATH or PATH depending on system (Posix or Windows) that is
> effective when the dlopen function is called. All OS'es where shared
> libraries are possible have something similar.
The variations among platforms are great enough that I
On Tue, Jun 08, 2004 at 12:44:22PM -0400, Andrew Dunstan wrote:
> This only applies to dev versions, as the library version is bumped each
> release, I believe.
Actually, the library version is not bumped each release --- in fact,
there has been at least one time in the past where the version _s
From: "Bruce Momjian" <[EMAIL PROTECTED]>
>
> I think the idea is that you want to specify the path in the config
> file, after the app has already started. I don't think you can modify
> the environment variable after the app has started, and even if you can,
> it seems simpler to just do it in o
> "Thomas Hallgren" <[EMAIL PROTECTED]> writes:
> > Why does postgres maintain a loader logic of its own? I can understand
that
> > the dynamic_library_path is necessary in order to configure everything
in
> > one single place. But why not just merge it with the LD_LIBRARY_PATH (or
> > PATH on Wind
Fabien COELHO wrote:
You get this error, pg_strcasecmp, when you have a different
libpgport library around instead of the CVS version. You need to
clean something out to fix it.
Isn't the "make check" supposed to used the new version of binaries
and libraries?
I investigated a little bit fol
I wrote:
Bruce Momjian wrote:
Can someone confirm that the newer 1.10 MinGW doesn't need the psql
print.c newline hack? If so, we can do a version test in that area and
mark it down as a mingw version-specific bug.
I assume you mean MSys 1.0.10 - I have that plus MinGW 3.1.0-1 these
are the la
You get this error, pg_strcasecmp, when you have a different libpgport
library around instead of the CVS version. You need to clean something
out to fix it.
Isn't the "make check" supposed to used the new version of binaries and
libraries?
I investigated a little bit following your hint:
Inde
Next Monday, we're going to put out a 7.4.3 release, incorporating all the
little patches that have been back-patched to date ... I just setup a cron
job that will build a nightly snapshot of 'stable', that is available on
the ftp server under /pub/stable_snapshot ...
If anyone has any patches
On 6/8/2004 11:49 AM, Robert Treat wrote:
Well I am working to address the problem, sorry if I am not doing it
fast enough. I spoke with the gborg maintainer and found out that the
top 5 is based on page views for a project rather than cvs activity.
Aha ... and let me guess, the algorithm does NOT
> [EMAIL PROTECTED] writes:
>> If I understand correctly, and I've sort of just worked on this
>> assumption, a sequence does not nessisarily produce a sequence of
>> numbers.
>> It produces a succession of numbers that are guarenteed to increase, but
>> not nessisarily with a specific interval (us
Well I am working to address the problem, sorry if I am not doing it
fast enough. I spoke with the gborg maintainer and found out that the
top 5 is based on page views for a project rather than cvs activity.
While I've no doubt you've been more active on slony development, I am
not so sure that pg
Bruce Momjian wrote:
Shridhar Daithankar wrote:
Andrew Dunstan wrote:
Shridhar Daithankar wrote:
Leaving it for a full build as I am calling it a day. Will give it
another go tomorrow morning..
What you would need to test is not #ifdefing the whole thing out -
rather you
"Thomas Hallgren" <[EMAIL PROTECTED]> writes:
> Why does postgres maintain a loader logic of its own? I can understand that
> the dynamic_library_path is necessary in order to configure everything in
> one single place. But why not just merge it with the LD_LIBRARY_PATH (or
> PATH on Windows) and t
Shridhar Daithankar wrote:
> Andrew Dunstan wrote:
>
> > Shridhar Daithankar wrote:
> >> Leaving it for a full build as I am calling it a day. Will give it
> >> another go tomorrow morning..
> >>
> >
> > What you would need to test is not #ifdefing the whole thing out -
> > rather you would ne
Fabien COELHO <[EMAIL PROTECTED]> writes:
> It seems that current cvs head regression tests are broken, at least on my
> debian laptop. That does not help with developping some new patch...
FWIW, I've seen no such problems...
regards, tom lane
---
On Tue, Jun 08, 2004 at 10:18:42 -0400,
[EMAIL PROTECTED] wrote:
>
> If I understand correctly, and I've sort of just worked on this
> assumption, a sequence does not nessisarily produce a sequence of numbers.
> It produces a succession of numbers that are guarenteed to increase, but
> not nessi
Bruce Momjian wrote:
Thomas Hallgren wrote:
Why does postgres maintain a loader logic of its own? I can understand that
the dynamic_library_path is necessary in order to configure everything in
one single place. But why not just merge it with the LD_LIBRARY_PATH (or
PATH on Windows) and then let
[EMAIL PROTECTED] writes:
> If I understand correctly, and I've sort of just worked on this
> assumption, a sequence does not nessisarily produce a sequence of numbers.
> It produces a succession of numbers that are guarenteed to increase, but
> not nessisarily with a specific interval (usually one
Fabien COELHO wrote:
>
> Dear hackers,
>
> It seems that current cvs head regression tests are broken, at least on my
> debian laptop. That does not help with developping some new patch...
>
> sh> uname -a
> Linux sablons 2.4.20-3-686 #1 Sat Jun 7 22:34:55 EST 2003 i686 GNU/Linux
> sh> ./config
> [EMAIL PROTECTED] writes:
>> The question is, what do you think of an "addval" function for
>> sequences.
>
> It would have to be defined as "do the same thing as N successive
> nextval calls would do", which would not be especially useful in the
> presence of caching.
>
>> The problem I, and I k
Thomas Hallgren wrote:
> Why does postgres maintain a loader logic of its own? I can understand that
> the dynamic_library_path is necessary in order to configure everything in
> one single place. But why not just merge it with the LD_LIBRARY_PATH (or
> PATH on Windows) and then let dlopen do the r
Dear hackers,
It seems that current cvs head regression tests are broken, at least on my
debian laptop. That does not help with developping some new patch...
sh> uname -a
Linux sablons 2.4.20-3-686 #1 Sat Jun 7 22:34:55 EST 2003 i686 GNU/Linux
sh> ./configure
sh> make
sh> cd src/test/regress
sh>
[EMAIL PROTECTED] writes:
> The question is, what do you think of an "addval" function for sequences.
It would have to be defined as "do the same thing as N successive
nextval calls would do", which would not be especially useful in the
presence of caching.
> The problem I, and I know many other
I guess I have to address a slightly broader audience, or do I conclude
from the total lack of interest in this matter that nobody cares if we
promote something here as one of our "top five" flagship projects, that
is inactive for years and still a prototype implementation against
PostgreSQL 6.
On 6/7/2004 2:33 PM, Jeff Davis wrote:
On Mon, 2004-06-07 at 06:20, Jan Wieck wrote:
I tend to agree with you that spurious SYNC's aren't the end of the
world. The idea of using notify to tell the syncThread somthing happened
is probably the right way to do it, but at this time a little invasive.
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Yeah, I looked into that when core started discussing this whole
>> thing awhile back. The Red Hat port of BZ to Postgres is perfectly
>> usable.
> Is it available anywhere?
Sure, download it off their front bugzilla page:
http:/
> [EMAIL PROTECTED] writes:
>> Anyway, I'm not quite getting the idea of caching sequence values. I
>> understand the performance benefits, but it seems problematic across
>> multiple backends, almost ensuring "holes" in the sequence of numbers.
>
> The point is to reduce lock contention on the seq
On Thu, 26 Feb 2004, Gavin Sherry wrote:
> Comments? Questions? Suggestions?
Is that plan that in the future one can split a single table into
different table spaces? Like storing all rows with year < 1999 in one
tablespace and the rest in another?
With the rule system and two underlying table
Why does postgres maintain a loader logic of its own? I can understand that
the dynamic_library_path is necessary in order to configure everything in
one single place. But why not just merge it with the LD_LIBRARY_PATH (or
PATH on Windows) and then let dlopen do the rest using a stripped filename?
> > And BTW, I was not running the regression in a cygwin shell.
> > It was a msys shell
> > only. I am thinking of knowcking off cygwin in favour of
> msys. But I
> > don't find CVS with msys.. I need to find a commandline cvs
> for daily
> > use. WinCVS is just too much GUI for my taste..
>
I'm trying to compile psql using MinGW but the only way to succeed with that
is apparently to configure "--without-readline". I've searched for a pure
MinGW port of the readline package and I found one at
http://sourceforge.net/projects/mingwrep/. Apparently it's too old. I also
tried to compile th
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Shridhar Daithankar
> Sent: 08 June 2004 08:34
> To: Andrew Dunstan
> Cc: PostgreSQL-development; [EMAIL PROTECTED]
> Subject: Re: [pgsql-hackers-win32] [HACKERS] Failures with
> windows port
>
Andrew Dunstan wrote:
Shridhar Daithankar wrote:
Leaving it for a full build as I am calling it a day. Will give it
another go tomorrow morning..
What you would need to test is not #ifdefing the whole thing out -
rather you would need to enable the fputc by removing the #ifndef and
#endif line
This is my first post to the dev list, so please be gentle. ;)
When using the current head of pgsql, I find four errors when running "make check".
They are all of the same nature, basically that the expected.out file has "syntax
error", where as psql is saying "parse error".
I have included th
59 matches
Mail list logo
