Bruce Momjian [EMAIL PROTECTED] writes:
From our previous discussion of 2-phase commit, there was concern that
the failure modes of 2-phase commit were not solvable. However, I think
multi-master replication is going to have similar non-solvable failure
modes, yet people still want
I have encoding problems using translated error messages (7.4beta1).
When database encoding is set to SQL_ASCII, all mesages arrive to client
correctly respecting the CLIENT_ENCODING, but if I create database WITH
ENCODING='unicode' or WITH ENCODING='latin2', messages are displayed
Bruce Momjian said:
Are all the IPv6 issues resolved in current CVS?
This one appears to be, at any rate.
cheers
andrew
-
--
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
OK, now we are getting
I said:
This doesn't seem to quite square
with your explanation though --- surely the number should go to 8000 and
change? The man page for top says these numbers are in kilobytes ...
but if they were really measured in, say, 4K pages, then we'd be talking
about 26M of shared memory touched,
Because MinGW/Msys doesn't come with flex/bison by default, I have added
those derived files to the WIN32_DEV branch in CVS. It makes it easier
for people to install _just_ MinGW and compile PostgreSQL on Win32. The
branch will live for only 1-2 months until we start 7.5 development.
Those
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Are all the IPv6 issues resolved in current CVS?
AFAIK, yes ... but I don't run IPv6 here, so I might not be the best
authority on the subject ...
Completed unless more problem reports arrive --- that's great.
--
Bruce Momjian
Hi,
I just checked out the current CVS-version and everything is fine now on my
SuSE 8.2-box.
I set tcpip_socket in postgresql.conf to true and was able to connect to
localhost and 127.0.0.1. I added my local IPv4-netaddress to pg_hba.conf and
was able to connect to my networkadress.
Thank
On Wed, 10 Sep 2003, Bruce Momjian wrote:
Because MinGW/Msys doesn't come with flex/bison by default, I have added
those derived files to the WIN32_DEV branch in CVS. It makes it easier
for people to install _just_ MinGW and compile PostgreSQL on Win32. The
branch will live for only 1-2
Alvaro Herrera [EMAIL PROTECTED] writes:
On Wed, Sep 10, 2003 at 07:27:02AM -0400, Andrew Dunstan wrote:
If someone can spoof the packet address isn't there also a possibility
that they can read your packets and see your random signature?
Spoofing the packet source address is not quite the
From our previous discussion of 2-phase commit, there was concern that
the failure modes of 2-phase commit were not solvable. However, I think
multi-master replication is going to have similar non-solvable failure
modes, yet people still want multi-master replication.
No. The real
Marc G. Fournier wrote:
On Wed, 10 Sep 2003, Bruce Momjian wrote:
Because MinGW/Msys doesn't come with flex/bison by default, I have added
those derived files to the WIN32_DEV branch in CVS. It makes it easier
for people to install _just_ MinGW and compile PostgreSQL on Win32. The
Bruce Momjian wrote:
I assume we never came to a final conclusion on how to do CREATE
FUNCTION without double-quoting.
---
Many discussions, but no final conclusion in sight, it seems. That
\beginliteral stuff is psql
On Wed, Sep 10, 2003 at 07:04:13PM +0200, Andreas Pflug wrote:
Bruce Momjian wrote:
I assume we never came to a final conclusion on how to do CREATE
FUNCTION without double-quoting.
Many discussions, but no final conclusion in sight, it seems. That
\beginliteral stuff is psql centric,
Darko Prenosil writes:
I have encoding problems using translated error messages (7.4beta1).
When database encoding is set to SQL_ASCII, all mesages arrive to client
correctly respecting the CLIENT_ENCODING, but if I create database WITH
ENCODING='unicode' or WITH ENCODING='latin2',
Alvaro Herrera wrote:
On Wed, Sep 10, 2003 at 07:04:13PM +0200, Andreas Pflug wrote:
Bruce Momjian wrote:
I assume we never came to a final conclusion on how to do CREATE
FUNCTION without double-quoting.
Many discussions, but no final conclusion in sight, it seems. That
Philip Yarra [EMAIL PROTECTED] writes:
On Wed, 10 Sep 2003 02:15 pm, Bruce Momjian wrote:
This would be a pretty short list unless I count wrong! This excludes all
releases of FreeBSD (and I'm willing to bet other BSDs), Solaris (at least
the old version I have), OSF, Linux, and who knows
I wrote:
I found a few notices and warnings that inform you that the command you
are executing has no effect because the object is already in the state you
want it. I think these are useless, and there is also some inconsistency.
Does someone want to defend keeping them?
I take it that
On Wed, Sep 10, 2003 at 12:49:31 -0400,
Tom Lane [EMAIL PROTECTED] wrote:
The question is whether any of this is worth worrying about in PG.
ISTM the correct solution to such a risk is to tighten your kernel's
packet filtering, not harden one piece of one application.
On linux at least, it
On Wed, Sep 10, 2003 at 07:04:13PM +0200, Andreas Pflug wrote:
I assume we never came to a final conclusion on how to do CREATE
FUNCTION without double-quoting.
Many discussions, but no final conclusion in sight, it seems. That
\beginliteral stuff is psql centric, where a sql syntax
I'm not sure if this should be considered a bug or not. At least in my case it
doesn't cause a problem. I think it could always be worked around with
explicit casts in any case, it just seems... wrong:
db= create or replace function array_length(integer[]) returns integer
as 'SELECT
On second thought, it does cause a problem:
db= create table aa (aa integer[]);
CREATE TABLE
db= select distinct(array_length(aa)) from aa;
ERROR: function array_upper(integer[]) does not exist
HINT: No function matches the given name and argument types. You may need to add
explicit
I've notice when trying to uninstall by using the
command
gmake uninstall, I still could access my database,
and also all my directories of postgresql and bin
files are still there!
I am not sure if I should first drop my database, but
even when I did this all my postgres directoires
remain there.
Tom wrote:
At this point it should move to pghackers, I think.
(responding to a patch for ISO 8601 Time Intervals in pgsql-patches)
Looks like I'll take a shot at more broadly hacking the postgresql
time interval code. Before doing so, I wanted to ask opinions
regarding what the right
On third though ignore this whole thread. I can't read.
sigh.
--
greg
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Dear List,
I already asked my question on the admin list, but got no answer. As I
even could not find any related information anywhere, I think my
question is a wish:
Would it be possible to set the maximum number of connections to each
database individually? I need this because the server
Nico King writes:
I've notice when trying to uninstall by using the
command
gmake uninstall, I still could access my database,
It only removes the files, it does not stop the server.
and also all my directories of postgresql and bin
files are still there!
It only removes files, not
I can confirm that this bug still exists in current CVS. The problem is
that CREATE SCHEMA AUTHORIZATION test is translated into SET SESSION
AUTHORIZATION 'test'; CREATE SCHEMA test;.
While this does allow the schema to be owned by 'test', it assumes
'test' has permissions to create the
I assume the attached patch is what you want done to fix this. Applied.
It quotes table names for vacuum and analyze, and uppercases the
keywords for clarity.
---
Matthew T. O'Connor wrote:
Ouch... sorry, my fault. I'll
On Wed, Sep 10, 2003 at 11:48:58 -0700,
Ron Mayer [EMAIL PROTECTED] wrote:
Looks like I'll take a shot at more broadly hacking the postgresql
time interval code. Before doing so, I wanted to ask opinions
regarding what the right behavior is of various timestamp/interval
operations.
Can
Peter Eisentraut wrote:
Tom Lane writes:
If we follow Peter's recently proposed guideline, this would have to be
a NOTICE not a WARNING, because the command absolutely is doing what you
told it to do. Peter, does that make you uncomfortable?
The message itself makes me a bit
Andrew Dunstan wrote:
Alvaro Herrera wrote:
On Wed, Sep 10, 2003 at 07:04:13PM +0200, Andreas Pflug wrote:
Bruce Momjian wrote:
I assume we never came to a final conclusion on how to do CREATE
FUNCTION without double-quoting.
Many discussions, but no final conclusion in sight,
On Wed, 2003-09-10 at 20:22, bognár, attila wrote:
Would it be possible to set the maximum number of connections to each
database individually? I need this because the server will be shared
between several users and I want to avoid that that somebody uses the
maximum number of connections
- Original Message -
From: Peter Eisentraut [EMAIL PROTECTED]
To: Darko Prenosil [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, September 10, 2003 7:20 PM
Subject: Re: [HACKERS] Trouble with error message encoding
Darko Prenosil writes:
I have encoding problems using
On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
I never agreed that a client solution would be satisfying. While
frontends might try to hide some uglyness of the syntax to the user for
single functions, editing large scripts with many functions is still
suffering from
Alvaro Herrera wrote:
On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
I never agreed that a client solution would be satisfying. While
frontends might try to hide some uglyness of the syntax to the user for
single functions, editing large scripts with many functions is still
On Wed, 10 Sep 2003, Alvaro Herrera wrote:
On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
I never agreed that a client solution would be satisfying. While
frontends might try to hide some uglyness of the syntax to the user for
single functions, editing large scripts
The problem with checking ownership of objects before dropping users is
that there's no way to check what objects depend on a user on another
database. But what if this information is stored in a shared relation?
Like pg_depend but only for shared objects.
--
Alvaro Herrera
Jeroen Ruigrok/asmodai wrote:
-On [20030905 20:52], Tom Lane ([EMAIL PROTECTED]) wrote:
Alternatively, find out what symbols your compiler predeclares.
If my theory is right then your pg_config_os.h file is failing to
define HAS_TEST_AND_SET; why?
Indeed, pg_config_os.h does not set
Jon Jensen [EMAIL PROTECTED] writes:
On Wed, 10 Sep 2003, Alvaro Herrera wrote:
On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
I never agreed that a client solution would be satisfying. While
frontends might try to hide some uglyness of the syntax to the user for
Bruno wrote:
Can you document which part of a mixed interval (with both months and
seconds parts) gets added first to a timestamp? I haven't ever run
across anything which says which gets done first.
In the existing code, the sql spec, or the proposed implementation?
In the existing code,
Greg Stark wrote:
Could the function bodies be shipped over using the new FE protocol as
parameters? That would eliminate the quoting and simplify matters for DBI and
other drivers as well.
Oh no, not this discussion again.
A whole script containing any number of valid statements must be
On Thu, Sep 11, 2003 at 01:05:47AM +0200, Andreas Pflug wrote:
Greg Stark wrote:
Could the function bodies be shipped over using the new FE protocol as
parameters? That would eliminate the quoting and simplify matters for DBI
and other drivers as well.
Oh no, not this discussion again.
Alvaro Herrera [EMAIL PROTECTED] writes:
On Thu, Sep 11, 2003 at 01:05:47AM +0200, Andreas Pflug wrote:
A whole script containing any number of valid statements must be
executable without interpreting the script.
How is that relevant? It's still parseable with parameter placeholders in
Andreas Pflug wrote:
I never agreed that a client solution would be satisfying. While
frontends might try to hide some uglyness of the syntax to the user
for single functions, editing large scripts with many functions is
still suffering from massive quotes.
Yes, I agree that a psql-specific
On Wed, Sep 10, 2003 at 15:43:56 -0700,
Ron Mayer [EMAIL PROTECTED] wrote:
Bruno wrote:
Can you document which part of a mixed interval (with both months and
seconds parts) gets added first to a timestamp? I haven't ever run
across anything which says which gets done first.
In
On Wed, 10 Sep 2003 02:39 pm, Tom Lane wrote:
A thread-safe implementation of
libpq is of zero value to an application unless it also has thread-safe
implementations of the other libraries it depends on.
Not necessarily so - we've managed okay so far (several years) working on
platforms
Bruno wrote:
...An interval has two parts... the number of months...and...the number of
seconds...if both parts are nonzero it makes a difference in which part
gets added first. For example '2003-02-28'::date + '1 month 1 day'::interval
might be either 2003-03-29 or 2003-04-01. In 7.4 it is
Jon Jensen [EMAIL PROTECTED] writes:
On Wed, 10 Sep 2003, Alvaro Herrera wrote:
On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
I never agreed that a client solution would be satisfying. While
frontends might try to hide some uglyness of the syntax to the user for
Andreas Pflug [EMAIL PROTECTED] writes:
Bruce Momjian wrote:
I assume we never came to a final conclusion on how to do CREATE
FUNCTION without double-quoting.
Many discussions, but no final conclusion in sight, it seems. That
\beginliteral stuff is psql centric, where a sql syntax solution
On Wed, 2003-09-10 at 15:57, Bruce Momjian wrote:
I assume the attached patch is what you want done to fix this. Applied.
It quotes table names for vacuum and analyze, and uppercases the
keywords for clarity.
Yeah, this is basically what I meant, sorry I didn't get to it quicker.
However,
-On [20030909 00:42], Tom Lane ([EMAIL PROTECTED]) wrote:
IIRC, Oracle does not have rollback-able DDL. That might imply that the
reason they have MODIFY CONSTRAINT is that in Oracle you can't use the
above way to eliminate the window. Can you put ALTERs inside
transactions at all in Oracle?
As
51 matches
Mail list logo
