Le Vendredi 21 Novembre 2003 19:47, Tom Lane a Ãcrit :
> I think the main value of a build farm is that we'd get nearly immediate
> feedback about the majority of simple porting problems. ÂYour previous
> arguments that it wouldn't smoke everything out are certainly valid ---
> but we wouldn't aban
Main needs partitioning is useful for:
- partition elimination for queries (e.g. seq scans only scan relevant partitions)
- deleting/detaching huge parts of a table in seconds
- attaching huge parts to a table in seconds (that may have been loaded with
a fast loading utility (e.g. loading
Jean-Michel POURE wrote:
Le Vendredi 21 Novembre 2003 19:47, Tom Lane a Ãcrit :
I think the main value of a build farm is that we'd get nearly immediate
feedback about the majority of simple porting problems. Your previous
arguments that it wouldn't smoke everything out are certainly valid -
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Besides, it's a tad odd to see files that are marked group writable but
>> not owner writable. You've got to agree there's not much sense in that.
> How else are you going to commit files? /usr/bin/cvs is not setuid,
Sure, but a
Andrew Dunstan wrote:
Jean-Michel POURE wrote:
Le Vendredi 21 Novembre 2003 19:47, Tom Lane a Ãcrit :
I think the main value of a build farm is that we'd get nearly
immediate
feedback about the majority of simple porting problems. Your previous
arguments that it wouldn't smoke everything o
On Mon, 2003-11-24 at 01:07, Christopher Kings-Lynne wrote:
> Hi,
>
> Is there demand for this syntax:
>
> ALTER SEQUENCE ON table(col) CYCLE 100;
>
> It would allow us to become sequence-name independent...
I think the right approach to this problem would be to implement
IDENTITIES and GENERAT
Le Lundi 24 Novembre 2003 16:38, Andreas Pflug a Ãcrit :
> And a tiny correction: The farm member for win32 is my machine, and it's
> operated manually :-)
Some GNU/Linux farm animals are living in my garage running on very old 50
euros machines ... Ancient farming :-)
By the way, we would love
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Is there demand for this syntax:
>
> ALTER SEQUENCE ON table(col) CYCLE 100;
What if the values in a column are generated via a sequence that was
created independently -- i.e. it's not a SERIAL column?
I'm not very enthusiastic about features
With a recent snapshot of CVS HEAD:
make[1]: Leaving directory `/home/nconway/build-pgsql-cvs/src/backend/parser'
gcc -O0 -g -Wall -Wmissing-prototypes -Wmissing-declarations
-I/home/nconway/pgsql/src/interfaces/libpq -I../../../src/include
-I/home/nconway/pgsql/src/include -D_GNU_SOURCE -DBIND
Hi all,
I know you're all busy with 7.4 comming out and I was wondering if some
one could have an idea about the following:
I host a game that does a HEAVY use of postgresql working like a charm.
But when the server is a little busy (like when Marc approves a WAG of
mail), postgresql dosn't respo
GCC supports the -Wshadow command-line option:
-Wshadow
Warn whenever a local variable shadows another local
variable, parameter or global variable or whenever a
built-in function is shadowed.
Currently, enabling this for the PostgreSQL tree produces a lot
Neil Conway <[EMAIL PROTECTED]> writes:
> String literals with embedded newline have been deprecated for a
> couple GCC releases, and are no longer supported.
[grumble] ... the great thing about gcc is there are so many
incompatible versions to choose from.
I fixed the occurrence at pg_dump.c lin
Hi,
seems for regexp which works in 7.3 is failing in 7.4.
Is't possible to configure pgsql to be compatible with 7.3 regexp ?
Welcome to psql 7.3.4, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal
Neil Conway <[EMAIL PROTECTED]> writes:
> GCC supports the -Wshadow command-line option:
>-Wshadow
>Warn whenever a local variable shadows another local
>variable, parameter or global variable or whenever a
>built-in function is shadowed.
> Currently, en
On Mon, Nov 24, 2003 at 12:25:32PM -0500, Neil Conway wrote:
> If there are any other GCC warning flags anyone else feels would be
> useful, let me know.
I find the following also useful:
-Wcast-align
-Wcast-qual
-Wpointer-arith
-Wstrict-prototypes
And maybe:
-Waggregate-return
Kurt
-
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> seems for regexp which works in 7.3 is failing in 7.4.
> Is't possible to configure pgsql to be compatible with 7.3 regexp ?
SET regex_flavor TO extended;
> www=# select 'problem' ~ '^\\p';
> ERROR: invalid regular expression: invalid escape \ sequence
Zeugswetter Andreas SB SD kirjutas E, 24.11.2003 kell 13:16:
> Main needs partitioning is useful for:
> - partition elimination for queries (e.g. seq scans only scan relevant partitions)
> - deleting/detaching huge parts of a table in seconds
> - attaching huge parts to a table in seconds (that may
Some systems that can run 32-bit and 64-bit executables have lib64
directories alongside lib directories. (You could also imagine any other
alternative compilation mode in place of "64".) This requires some
adjustments in the PostgreSQL build system.
Currently, when you specify --with-openssl, t
Tom Lane <[EMAIL PROTECTED]> writes:
> Neil Conway <[EMAIL PROTECTED]> writes:
>> Currently, enabling this for the PostgreSQL tree produces a lot of
>> warnings.
>
> How many is "a lot"?
Maybe a couple hundred or so, but most of the warnings are derived
from a few globals with common names -- I wo
OK, I've been spreading rumours about fixing the internationalization
problems, so let me make it a bit more clear. Here are the problems that
need to be fixed:
- Only one locale per process possible.
- Only one gettext-language per process possible.
- lc_collate and lc_ctype need to be held fi
On Sat, 2003-11-22 at 11:43, Nigel J. Andrews wrote:
> On Wed, 19 Nov 2003, Joshua D. Drake wrote:
>
> > 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
Tom Lane <[EMAIL PROTECTED]> writes:
> I wouldn't object to something that catches shadowings of parameters
> or local variables, but I think the flag as defined is not very
> useful.
On closer examination, that seems like a prescient comment. There are
about 1100 distinct warnings enabled by this
On Mon, 24 Nov 2003, Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > seems for regexp which works in 7.3 is failing in 7.4.
> > Is't possible to configure pgsql to be compatible with 7.3 regexp ?
>
> SET regex_flavor TO extended;
aha, thanks a lot
>
> > www=# select 'problem' ~ '
Lamar Owen <[EMAIL PROTECTED]> wrote:
> Sander Steffann has built Red Hat 6.2, 7.3, 9, and RHEL 2.1 RPM's
> for me, and I have uploaded them. The release is different; 0.3PGDG
> and 0.4PGDG. I will be looking at his spec file differences and
> updating the source RPM soon. The binary RPM for Fed
Neil Conway writes:
> The problem with #2 is the large number of warnings induced by system
> headers: other platforms / standard libraries may well cause
> additional instances of shadowing, so it might take a little while to
> track down all the spurious warnings.
Yes, that's what I'm afraid of
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I'm not sure what the point is anyway. Shadowing is perfectly
> well-defined and I've never heard of a real problem because of it.
Well, shadowing a formal parameter with a local variable is most likely
a mistake, and shadowing a local with a more-ti
Robert Treat <[EMAIL PROTECTED]> writes:
> Seems merging the two would work... attlogpos, the attributes
> logical position.
Unless anyone has any further objections, I'll switch to using attlogpos.
-Neil
---(end of broadcast)---
TIP 2: you can ge
Tom Lane <[EMAIL PROTECTED]> writes:
> This is a backwards-compatibility hangover.
> But I'd not want to break it just because someone thinks the hack is
> ugly. It was ugly from day one.
I agree it shouldn't be removed -- I was just curious to see what was
using it. It's certainly ugly, though.
FYI, the HP testdrive farm, http://www.testdrive.hp.com, has shared
directories for most of the machines, meaning you can CVS update once
and telnet in to compile for each platform.
---
Andrew Dunstan wrote:
> Tom Lane wrote
Joshua D. Drake wrote:
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
Peter Eisentraut wrote:
I was at the ObjectWeb Conference today; ObjectWeb
(http://www.objectweb.org) being a consortium that has amassed quite an
impressive array of open-source, Java-based middleware under their
umbrella, including for instance our old friend Enhydra. And they
regularly kept men
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Is it easy to do a quick message change to state that it was the IPv6
> > socket that failed?
>
> I deliberately did not do that because we were well past error message
> freeze for 7.4, but we certainly should fix it for 7.5.
Y
On Wed, Nov 19, 2003 at 04:34:27PM +0100, Peter Eisentraut wrote:
> Hence the open-source community approach. Closed-source development teams
> can do all the above, with great effort. But by throwing out the code and
> have real people test them on real systems with real applications, you can
>
Would it be reasonable to promote users testing daily snapshots with
popular applications? I'm guessing there's not many applications that
have automated test frameworks, but any that do would theoretically
provide another good test of PGSQL changes.
May I quote Joel on Software here?
http://www.j
On Fri, Nov 21, 2003 at 01:32:38PM -0500, Jan Wieck wrote:
> bootstrap mode to apply the changes, could be an idea to think of. It
> would still require some downtime, but nobody can avoid that when
> replacing the postgres binaries anyway, so that's not a real issue. As
> long as it eliminates
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, I am unsure why the mention of IPv6 was removed from the original
> patch I submitted. Does anyone remember?
You sure you aren't confusing this code with the listen-socket-opening
code over in backend/libpq/ ?
The libpq code identifies the socket
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Yes, I am unsure why the mention of IPv6 was removed from the original
> > patch I submitted. Does anyone remember?
>
> You sure you aren't confusing this code with the listen-socket-opening
> code over in backend/libpq/ ?
>
> The l
Quoth [EMAIL PROTECTED] ("Jim C. Nasby"):
> On Fri, Nov 21, 2003 at 01:32:38PM -0500, Jan Wieck wrote:
>> bootstrap mode to apply the changes, could be an idea to think of. It
>> would still require some downtime, but nobody can avoid that when
>> replacing the postgres binaries anyway, so that's
Bruce Momjian writes:
> FYI, the HP testdrive farm, http://www.testdrive.hp.com, has shared
> directories for most of the machines, meaning you can CVS update once
> and telnet in to compile for each platform.
Except that you can't open connections to the outside from these machines.
--
Peter E
Sander Steffann has built Red Hat 6.2, 7.3, 9, and RHEL 2.1 RPM's for me, and
I have uploaded them. The release is different; 0.3PGDG and 0.4PGDG. I will
be looking at his spec file differences and updating the source RPM soon.
The binary RPM for Fedora will remain at 0.2PGDG for now.
If you
40 matches
Mail list logo
