> Where can I get a Postscript version docs for 7.1?
I'll start building hardcopy in the next day or two, and hope that it
will be done quickly (more quickly that in previous releases). Will keep
y'all informed on the progress...
- Thomas
---(end of
> I've noticed a pg_dump/pg_dumpall problem with timestamp variables, in
> dumping the minute, and second values:
> instead of dumping
> 12:01:00.00 it dumps out 12:60:00.00 which is not accepted when
> restoring a database...
You are running the Mandrake distro, or somehow compiling with a bad s
> so it isn't a "fictitous crowd" that is going with the smaller chunks ...
> its about 30% on a very small sample ...
(back in town from the weekend, to see the PostgreSQL tarball ripped to
shreds ;)
Peter, I'm with you on this. If folks want to help support PostgreSQL by
providing subset-tarba
[ Charset ISO-8859-1 unsupported, converting... ]
> I like this. Ensure that tips can be dumped into a log file --
> preferably separate from the main one -- so it can be run on a live
> system for a short period of time, recorded then analyzed later.
Yes, they would go into the standard postmas
My idea was to have PostgreSQL output tips to help performance. The
TODO item is:
* Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
ANALYZE, and CLUSTER
I also will be writing an article on performance tuning this month.
What parameters would these op
Hi guys,
Just thinking about the future directions PostgreSQL is taking, and it
seems (just a feeling) like most people prefer it to be as self tuning
as possible.
In trying to think about how it will/would do that I think PostgreSQL
will need to know "how much" of the resources of the server it
Regression tests for Yellow Dog Linux (PPC RedHat derivative) failed all
over the place with 7.0.3. Passed smoothly with 7.1RC3, though. I've
got details if anybody's curious.
-nat
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaste
Where can I get a Postscript version docs for 7.1?
--
Tatsuo Ishii
> Ladies and Gentlemen ...
>
> Its been a long, arduous, up hill battle to get to this point, with all of
> the changes since v7.0 was released, but we're finally there ...
>
>
> The PostgreSQL Global Development Group is *plea
The Hermit Hacker wrote:
> We do, we follow the scheme as used by ... the BSD camp :) Be thankful we
> don't go all the way and use 7.2-RELEASE too :)
If we had 7.1-CURRENT, 7.1-RELEASE, and 7.1-STABLE, the versioning
comparision would be just fine -- better than now. As it stands, an
upgrade f
Peter Eisentraut wrote:
> Coupla issues:
> I'm confused about the logging. You install a logrotate configuration
> which talks about a file /var/log/postgresql, but the spec file creates a
> directory /var/log/pgsql/
I'll correct that. The logrotate script (which I guess to prevent
confusion s
Lamar Owen writes:
> Uploaded. Please take a look.
>
> ftp://ftp.postgresql.org/pub/dev/test-rpms
>
> There _are_ changes. I will detail the changes for the RC4 RPMset.
Coupla issues:
I'm confused about the logging. You install a logrotate configuration
which talks about a file /var/log/post
Hi--
This is my first time at using Postgress , and I would like to install it
on a Win 2000 machine .HELP !!!
Thanks
Nadim
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail comma
I believe what we are talking about is diff,
I am trying to install pltcl language on my db not pgmonitor.
When I wand to build a pltcl.so, I got following msg,
I want to know there's any wrong?
Thanks anyway.
Jie LIANG
St. Bernard Software
10350 Science Center Drive
Suite 100, San Diego, CA
Hi--
This is my first time at using Postgress , and I would like to install it
on a Win 2000 machine .HELP !!!
Thanks
Nadim
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.ht
matthew green <[EMAIL PROTECTED]> writes:
> i also believe the `Bad address' errors were caused when the test
> was run in an NFS mounted directory.
You may have something, there. My test run on the VAX was over NFS.
I set up NetBSD on a VAX specifically to test PostgreSQL 7.1, but I
didn't hav
this only represents since 8:30am this morning ...
/source/v7.0.3/postgresql-7.0.3.support.tar.gz => 9
/source/v7.0.3/postgresql-7.0.3.test.tar.gz => 3
/source/v7.0.3/postgresql-7.0.3.docs.tar.gz => 10
/source/v7.0.3/postgresql-7.0.3.tar.gz => 22
/source/v7.0.3/postgresql-7.0.3.base.tar.gz => 9
On Sun, 8 Apr 2001, Oliver Elphick wrote:
> The Hermit Hacker wrote:or development:
> >>
> >> That means the final release of 7.1 will be called 7.2. Bugfix releases
> >> will then be 7.2.x. Meanwhile new development versions will be 7.3.x
> >> which will finally be released as 7.4, and
On Sun, 8 Apr 2001, Peter Eisentraut wrote:
> I wrote:
>
> > Since people suddenly seem to be suffering from bandwidth concerns I have
> > devised a new distribution split to address this issue. I propose the
> > following four sub-tarballs:
>
> > * postgresql-XXX.base.tar.gz3.3 MB
> > *
Bruce Momjian writes:
> I didn't know that. I thought we genarated postscript only major
> releases. Do we regenerate HTML for subreleases?
The HTML is generated every 12 hours, and whenever a distribution is
wrapped up it picks up the latest bundle. This will probably have to be
sorted out ag
The Hermit Hacker wrote:or development:
>>
>> That means the final release of 7.1 will be called 7.2. Bugfix releases
>> will then be 7.2.x. Meanwhile new development versions will be 7.3.x
>> which will finally be released as 7.4, and so on...
>
>Not in this life time ... we are not
I wrote:
> Since people suddenly seem to be suffering from bandwidth concerns I have
> devised a new distribution split to address this issue. I propose the
> following four sub-tarballs:
> * postgresql-XXX.base.tar.gz 3.3 MB
> * postgresql-XXX.opt.tar.gz 1.7 MB
> * postgresql-XXX.docs.tar.g
On Sun, 8 Apr 2001, Oliver Elphick wrote:
> The Hermit Hacker wrote:
> >On Sat, 7 Apr 2001, Lamar Owen wrote:
> >
> >> One quick note -- since 'R' < 'b', the RC RPM's must be forced to
> >> install with --oldpackage, as RPM does a simple strcmp of version
> >> numbers -- 7.1RC3 < 7.1bet
Christopher Sawtell writes:
> For me and I expect many other folk on the edge of civilization it is a
> total PITA to have to fiddle around and download many separate tarball
> files. What I want is to be able to start a d/l going and then come back
> when it's finished and know that I have _ever
The Hermit Hacker writes:
> ... and get rid of the *large* file, which will
> save all the mirrors a good deal of space over time ...
You will certainly get a furious crowd at your door within hours if you do
that, as the follow-ups show. Saving download bandwidth is a valid issue,
but saving d
The Hermit Hacker writes:
> On Sat, 7 Apr 2001, Lamar Owen wrote:
>
> > One quick note -- since 'R' < 'b', the RC RPM's must be forced to
> > install with --oldpackage, as RPM does a simple strcmp of version
> > numbers -- 7.1RC3 < 7.1beta1, for instance. Just force it with
> > --oldpackage if y
The Hermit Hacker wrote:
>On Sat, 7 Apr 2001, Lamar Owen wrote:
>
>> One quick note -- since 'R' < 'b', the RC RPM's must be forced to
>> install with --oldpackage, as RPM does a simple strcmp of version
>> numbers -- 7.1RC3 < 7.1beta1, for instance. Just force it with
>> --oldpackage
26 matches
Mail list logo
