[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser, but there is
lots of
Marc G. Fournier wrote:
On Wed, 2 Apr 2003, scott.marlowe wrote:
If that is a real objective, I'm surprised.
The base source tree has always been as BSD pure as we can make it ... its
never been kept a secret ...
True. But not linking to LGPLd libs would be a bit extreme
Hannu Krosing wrote:
[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser,
Tom Lane wrote:
On other Unixoid systems you can link against BSD-license libc code, or
some-random-proprietary-license code from HP or Sun or whomever. glibc
doesn't have a monopoly in that sphere. But mlw is offering code that
will *only* run against a single implementation that is LGPL
[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser, but there is
lots
I have been planning to test the whole thing with a few .NET
applications. I am currently using expat to parse the output to ensure
that it all works correcty.
That, unfortunately, probably implies that your implementation is almost
totally non-interoperable.
You should put out of your
Jan Wieck wrote:
Marc G. Fournier wrote:
On Wed, 2 Apr 2003, scott.marlowe wrote:
If that is a real objective, I'm surprised.
The base source tree has always been as BSD pure as we can make it ... its
never been kept a secret ...
True. But not linking to LGPLd libs
mlw wrote:
Jan Wieck wrote:
[...]
screen? We have a pure BSD alternative that we could even ship with our
distro, time to retire the libreadline hooks.
I certainly didn't want to open up this can of worms, that's for sure.
I have an amount of code that is LGPL, I would rather use it
Lamar Owen [EMAIL PROTECTED] writes:
And its stubs are in the backend, of all places.
Really? I must have missed that.
On Linux as compiled in Red Hat 9, at least:
[EMAIL PROTECTED] lowen]$ ldd /usr/bin/postgres
libreadline.so.4 = /usr/lib/libreadline.so.4 (0x401c6000)
That's
on one of the AIX4.3.3,
the 7.1.3 pgsql is installed by root on the system,
then I tried to install
7.3.1/or 7.3.2 under another non-root user,
I can run make, make check, make install,
postmaster can start without errors, but when
I try to createdb, here're some errors -
createdb emrxdbs
on one of the AIX4.3.3,
the 7.1.3 pgsql is installed by root on the system,
then I tried to install
7.3.1/or 7.3.2 under another non-root user,
I can run make, make check, make install,
postmaster can start without errors, but when
I try to createdb, here're some errors -
createdb
I already set the 2nd port for the new
installation, otherwise, postmaster will not
start up ...
johnl
-Original Message-
From: Christoph Haller [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 11:05 AM
To: John Liu
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] can't create
Since now is the time for contrib/ flamewars, this seemed a good time
to suggest this.
My colleague, Sorin Iszlai, wrote us a little program for rotating
our Postgres logs. It reads stdout and stderr, and sends them to
different files (and rotates them as necessary). It is currently
John Liu [EMAIL PROTECTED] writes:
I already set the 2nd port for the new
installation, otherwise, postmaster will not
start up ...
But your client-side programs are still talking to the port where the
old postmaster is.
You could set PGPORT in their environment to fix that. What I find more
On Thu, Apr 03, 2003 at 07:54:13AM -0500, [EMAIL PROTECTED] wrote:
I have been planning to test the whole thing with a few .NET
applications. I am currently using expat to parse the output to ensure
that it all works correcty.
That, unfortunately, probably implies that your
mlw wrote:
Jan Wieck wrote:
[...]
screen? We have a pure BSD alternative that we could even ship with
our distro, time to retire the libreadline hooks.
I certainly didn't want to open up this can of worms, that's for sure.
I have an amount of code that is LGPL, I would rather use it
[EMAIL PROTECTED] writes:
If I find a wiz-bang library that allows me to do something cool very
easily, and I write a some code that would be good for postgresql's contrib,
are you saying that it would not be usable because of the requirement of the
library that is not included on standard
[EMAIL PROTECTED] wrote:
The issue is:
Is the requirement of an LGPL library that is more than likely not already
on your system a disqualification for a contrib function?
Yes.
Because the requirement of something that is more likely not found on
usual installations TOGETHER WITH that it
Andrew Sullivan [EMAIL PROTECTED] writes:
Is anyone interested in having pglog-rotator?
FWIW, I saw an early version of pglog-rotator about a year and a half
ago (while consulting for LibertyRMS), and thought at the time that
it was pretty cool. So I'm for including it ... maybe even as
[EMAIL PROTECTED] writes:
We have taken a policy decision to keep the PG core distribution
(including contrib) straight BSD license --- and in my mind that
definitely includes not depending on any outside functionality that is
both (a) essential and (b) not available anywhere as BSD-license
On Thursday 03 April 2003 09:29, Tom Lane wrote:
Lamar Owen [EMAIL PROTECTED] writes:
And its stubs are in the backend, of all places.
Really? I must have missed that.
On Linux as compiled in Red Hat 9, at least:
[EMAIL PROTECTED] lowen]$ ldd /usr/bin/postgres
Lamar Owen [EMAIL PROTECTED] writes:
But it is in (and used by) psql (as of 7.3.2).
Certainly. I don't see a problem with that as far as the source
distribution goes; you can build it with readline, libedit, or neither.
Binary distributions are another matter. I think a pretty good case
could
Hi there,
I have been through the postgres faq's, and read through the describe.c
file.
I can't seem to solve my problem.
I am building an automatic file writer, that gives me information about each
of my tables.
What I need to know, is how to find out if a column is a primary, or part of
a
Hi all,
I have just tried this with the same result on default
full install of slackware 8.1 and 9.0.
After installation (and download of pgsql 7.3.2) i ran
these commands :
tar -xzvf postgresql-7.3.2.tar.gz
cd postgresql-7.3.2
./configure
(worked fine)
gmake
gmake then ran into a infinite
what command name would it being running under in my boxes service tree.
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Ferindo Middleton Jr [EMAIL PROTECTED] wrote:
I'm running Redhat Linux 8. I have registration to the Redhat
Network so I'm probably running the latest version of
where is the configuration file located. I'm running redhat linux 8
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Hi,
Tom Lane wrote:
It seems to me that it'd be fairly easy to make BEGIN cause only
a local state change in the backend; the actual transaction need not
start until the first subsequent command is received. It's already
true that the transaction snapshot is not frozen at BEGIN time, but
only
I'm running Redhat Linux 8. I have registration to the Redhat Network so
I'm probably running the latest version of postgre sql available. I also
have Redhat Databse v2.1 installed, but whenever I try to start a session,
I get the following error message:
psql: could not connect to server: No
On Thu, 3 Apr 2003 [EMAIL PROTECTED] wrote:
If I find a wiz-bang library that allows me to do something cool very
easily, and I write a some code that would be good for postgresql's
contrib, are you saying that it would not be usable because of the
requirement of the library that is not
Olleg Samojlov [EMAIL PROTECTED] writes:
As I can remember, already, when autocommit off transaction begin with
first DML or DDL command. May be better change client to use autocommit
off mode?
We've been waiting for those clients to get fixed for a long while.
Waiting for them to adopt
Would the plan be to add it to pg_ctl?
Andrew Sullivan [EMAIL PROTECTED] writes:
Is anyone interested in having pglog-rotator?
FWIW, I saw an early version of pglog-rotator about a year and a half
ago (while consulting for LibertyRMS), and thought at the time that
it was pretty cool. So
Steve [EMAIL PROTECTED] writes:
What I need to know, is how to find out if a column is a primary, or part of
a primary key. I need to do this using sql.
In 7.3 this is pretty easy: look in the pg_constraint table for a 'p'
constraint for the table. If you find one, 'conkey' lists the column
Andrew Gemmell [EMAIL PROTECTED] writes:
gmake then ran into a infinite loop
Check your system clock. I get the impression that the timestamp of the
configure file must be in the future compared to what your system thinks
the time is. So, every time it rebuilds config.status, it still finds
it
Tom Lane writes:
Andrew Sullivan expressed concern about this, too. The thing could
be made a little more failsafe if we made it impossible to set
ZERO_DAMAGED_PAGES to true in postgresql.conf, or by any means other
than an actual SET command --- whose impact would then be limited to
the
Andrew Gemmell writes:
gmake then ran into a infinite loop
i have piped gmake to a text file which shows where it
is looping etc.
this can be found at
http://www.stratocom.net/imos/pgsql-gmakelog.txt
Looks like the clock on your system or file system has a serious problem.
--
Peter
Jim Buttafuoco [EMAIL PROTECTED] writes:
Would the plan be to add it to pg_ctl?
You would not actually have to: you could just pipe pg_ctl's output to
pglog-rotator. But I think it'd be cool if pg_ctl had an option to use
pglog-rotator, or maybe even adopt it as standard behavior.
I think we
Does this log rotator do something that apache's doesn't?
Dave
On Thu, 2003-04-03 at 13:41, Tom Lane wrote:
Jim Buttafuoco [EMAIL PROTECTED] writes:
Would the plan be to add it to pg_ctl?
You would not actually have to: you could just pipe pg_ctl's output to
pglog-rotator. But I think
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
Andrew Sullivan expressed concern about this, too. The thing could
be made a little more failsafe if we made it impossible to set
ZERO_DAMAGED_PAGES to true in postgresql.conf, or by any means other
than an actual SET command ---
On Thu, Apr 03, 2003 at 13:26:01 -0500,
[EMAIL PROTECTED] wrote:
I don't know that it meets your criteria, but.
I have a set of scripts and a program that will load the US Census TigerUA
database into PostgreSQL. The thing is absolutely freak'n huge. I forget
which, but it is either
On Thu, Apr 03, 2003 at 01:41:08PM -0500, Tom Lane wrote:
You would not actually have to: you could just pipe pg_ctl's output to
pglog-rotator. But I think it'd be cool if pg_ctl had an option to use
pglog-rotator, or maybe even adopt it as standard behavior.
It's currently built to call a
On Thu, Apr 03, 2003 at 02:12:03PM -0500, Dave Cramer wrote:
Does this log rotator do something that apache's doesn't?
Probably not. This was just easier for us.
A little information might be handy here: we run postgres nder a
hosted environment, and we do not have root on the relevant boxes.
The IPv6 patch seems to still be a few bricks shy of a load. Grepping
for places that handle AF_INET but not AF_INET6 revealed these
unimplemented features:
1. IDENT authorization. Fails if either local or remote address is IPv6.
2. SSL. Postmaster allows SSL for AF_INET but not AF_INET6.
3.
On Thu, Apr 03, 2003 at 02:39:17PM -0500, Tom Lane wrote:
just not listing zero_damaged_pages in postgresql.conf.sample? We
already have several variables deliberately not listed there ...
Hey, that might be a good solution. Of course, it doesn't solve the
doomsday device problem, but nobody
On 2003-04-02 16:18:33 -0500, Tom Lane wrote:
Kevin Brown [EMAIL PROTECTED] writes:
Hmm...I don't know that I'd want to go that far -- setting this
variable could be regarded as a policy decision. Some shops may have
very good reason for running with ZERO_DAMAGED_PAGES enabled all the
Vincent van Leeuwen [EMAIL PROTECTED] writes:
... This cost us about 10 hours downtime. If I'd had the option I just
would've set ZERO_DAMAGED_PAGES to true and let it run for a few days to sort
itself out.
Yikes. If I understand this correctly, you had both critical data and
cache data in
On 2003-04-03 18:40:54 -0500, Tom Lane wrote:
Vincent van Leeuwen [EMAIL PROTECTED] writes:
... This cost us about 10 hours downtime. If I'd had the option I just
would've set ZERO_DAMAGED_PAGES to true and let it run for a few days to sort
itself out.
Yikes. If I understand this
On Thu, Apr 03, 2003 at 01:41:08PM -0500, Tom Lane wrote:
Andrew, could you toss up the script on pgsql-patches just so people can
take a look? Then we could think more about where to go with it.
Ok, the first try failed (of course) because I wasn't subscribed.
Should be there now, though.
A
Tom Lane wrote:
I've applied a patch to fix this, but can't try it out here for lack of
any IPv6 infrastructure ... please check it.
regards, tom lane
I tried it, and it works.
Regards,
Andreas
---(end of broadcast)---
TIP 2: you can get
At 05:28 PM 3/27/03 +0800, Christopher Kings-Lynne wrote:
There's no select * from table where pkey=x for insert; which would
block
on uncommitted inserts/updates of pkey=x and other selects for
insert/update.
How about user locks? Isn't there something in contrib/ for that??? I
could do a
so the only real solution to this now is in application code outside of a
transatction, i.e. PHP,Perl,VB,C,Python, etc, right?
Lincoln Yeoh wrote:
AFAIK the except select won't see other inserts in uncommitted
transactions. If those transactions are committed you will end up with
the same
AFAIK the except select won't see other inserts in uncommitted
transactions. If those transactions are committed you will end up with the
same problem. You can try it yourself, by manually doing two separate
transactions in psql.
You either have to lock the whole table, or lock at the
Josh Berkus wrote:
1) At least one main table with 12+ columns and 100,000+ rows
(each).
2) At least 10-12 additional tables of assorted sizes, at least half
of
which
should have Foriegn Key relationships to the main table(s) or each
other.
3) At least one large text or varchar field among
Folks,
Please pardon the cross-posting.
A small group of us on the Performance list were discussing the first steps
toward constructing a comprehensive Postgresql installation benchmarking
tool, mostly to compare different operating systems and file systemsm but
later to be used as a
Bruno Wolff III wrote:
On Thu, Apr 03, 2003 at 13:26:01 -0500,
[EMAIL PROTECTED] wrote:
I don't know that it meets your criteria, but.
I have a set of scripts and a program that will load the US Census TigerUA
database into PostgreSQL. The thing is absolutely freak'n huge. I forget
On Thu, Apr 03, 2003 at 17:19:13 -0500,
mlw [EMAIL PROTECTED] wrote:
I have a set of scripts, SQL table defs, a small C program, along with a
set of field with files that loads it into PGSQL using the copy from
stdin It works fairly well, but takes a good long time to load it all.
Jan Wieck wrote:PeerDirect tried to
contribute the Win32 port portion of their work to
the open source project.
The PostgreSQL global development team has
notyet made any final decision if or what parts of that code will or
willnot become part of the regular PostgreSQL distribution
Bruce
56 matches
Mail list logo
