On Thu, Oct 09, 2003 at 11:51:09PM -0400, Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > I'm seeing this compile warning on today's CVS tip:
> >
> > $ make src/backend/commands/tablecmds.o
> > gcc -O2 -g -Wall -Wmissing-prototypes -Wmissing-declarations -I./src/include
> > -D_GNU_SOURCE -c -o
On Mon, 2003-10-06 at 16:21, Joshua D. Drake wrote:
> postgres=# create user with encrypted password '98wq7912a';
> CREATE USER
> postgres=# create user with encrypted password '98wq7912a';
> ERROR: CREATE USER: user name "with" already exists
So, what are we doing about this? If we're considerin
CVS tip
WinXP/cygwin/gcc version 3.3.1 (cygming
special)
gives these
tablecmds.c:3528: warning: dereferencing
type-punned pointer will break strict-aliasing rulesexecQual.c:749: warning:
dereferencing type-punned pointer will break strict-aliasing
rulesexecQual.c:995: warning: derefe
The world rejoiced as [EMAIL PROTECTED] (Tatsuo Ishii) wrote:
> I'm tired of this kind of "2PC is too slow" arguments. I think
> Satoshi, the only guy who made a trial implementation of 2PC for
> PostgreSQL, has already showed that 2PC is not that slow.
I'm tired of it for a different reason, name
Isn't it great how you have the same directory on every host so you can
download once and run the same tests easily.
Neil Conway wrote:
> $ uname -a
> Linux spe170 2.4.17-64 #1 Sat Mar 16 17:31:44 MST 2002 parisc64 unknown
> $ gcc --version
> 3.0.4
>
> 'make check' passes
I didn't know there w
As you can see, we don't have many open items left.
---
P O S T G R E S Q L
7 . 4 O P E NI T E M S
Current at ftp://momjian.postgresql.org/pub/postgresql/open_
On Wed, 2003-10-08 at 21:44, Bruce Momjian wrote:
> Agreed. Do we set them all to -O2, then remove it from the ones we
> don't get successful reports on?
I took the time to compile CVS tip with a few different machines from
HP's TestDrive program, to see if there were any regressions using the
ne
Alvaro Herrera wrote:
> I'm seeing this compile warning on today's CVS tip:
>
> $ make src/backend/commands/tablecmds.o
> gcc -O2 -g -Wall -Wmissing-prototypes -Wmissing-declarations -I./src/include
> -D_GNU_SOURCE -c -o src/backend/commands/tablecmds.o
> src/backend/commands/tablecmds.c
> src
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Dawn M. Wolthuis) wrote:
> Good question. Although I would want to move away from relational
> databases too, if there is an RDBMS and one wants to query it, what
> would I aim for? If you look at XQuery, you will see an example of
>
Rod Taylor wrote:
- Start of PGP signed section.
> Below is a 7.2.4 example of the rserv log with inet data type. You will
> notice that inet cast to text, and the log entry are differently (one
> from unknown directly to text via a trigger, the other from inet cast to
> text).
>
> I see this has
Added to TODO:
* Prevent libpq's PQfnumber() from lowercasing the column name
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Agreed. We can add it to TODO. That is advertising the change.
>
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Where should I start on this? :-)
>
> Where should I start on all the people who are complaining now, but
> said not a word when the patch was put up for review?
>
> I'm quite annoyed at these claims that procedure wasn't followed.
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Where should I start on this? :-)
>
> Where should I start on all the people who are complaining now, but
> said not a word when the patch was put up for review?
>
> I'm quite annoyed at these claims that procedure wasn't followed.
Patch applied. Thanks.
---
Neil Conway wrote:
> On Sun, 2003-10-05 at 19:58, Tom Lane wrote:
> > That's a fairly useless place to put it, though, since someone would
> > only think to look at sort_mem if they already had a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Where should I start on this? :-)
Where should I start on all the people who are complaining now, but
said not a word when the patch was put up for review?
I'm quite annoyed at these claims that procedure wasn't followed.
It's either selective memory o
Andrew Dunstan wrote:
> There will be a new version out there soon. When I am happy with it I will
> let you know - right now I am dealing with 2 issues - setlocale(LC_ALL,"")
> doesn't read from the environment on Windows, and the program is possibly
> not picking up the buffers/connections proper
There will be a new version out there soon. When I am happy with it I will
let you know - right now I am dealing with 2 issues - setlocale(LC_ALL,"")
doesn't read from the environment on Windows, and the program is possibly
not picking up the buffers/connections properly.
Please don't put the vers
I'm for putting it in Win32... my 2c.
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Friday, 10 October 2003 11:39 AM
> To: Andrew Dunstan
> Cc: Postgresql Hackers; pgsql-hackers-win32
> Subject: Re: [pgsql-hackers-win32] [HACKERS] initdb
>
>
>
> I have add
I have added this URL to the Win32 page, and removed the "initdb C" TODO
item. Great job. Do you wantt this in Win32 CVS or should we just wait
for 7.5 to start?
---
Andrew Dunstan wrote:
>
> Excellent idea.
>
> Here's t
On Fri, 10 Oct 2003, Tatsuo Ishii wrote:
> > Yes. I don't think that 2PC is a solution for robustness in face of
> > network failure. It's too slow, to begin with. Some sort of
> > multi-master system is very desirable for network failures, &c., but
> > I don't think anybody does active/hot s
Tatsuo Ishii wrote:
> > Yes. I don't think that 2PC is a solution for robustness in face of
> > network failure. It's too slow, to begin with. Some sort of
> > multi-master system is very desirable for network failures, &c., but
> > I don't think anybody does active/hot standby with 2PC any more
> Yes. I don't think that 2PC is a solution for robustness in face of
> network failure. It's too slow, to begin with. Some sort of
> multi-master system is very desirable for network failures, &c., but
> I don't think anybody does active/hot standby with 2PC any more; the
> performance is too b
If anyone needs/wants access to UnixWare, let me know, I can make accounts
on mine.
LER
--On Thursday, October 09, 2003 17:19:30 -0700 "Joshua D. Drake"
<[EMAIL PROTECTED]> wrote:
Hello,
I have a solaris machine we could throw up for the community as well if
required.
Sincerely,
Joshua Dra
Hello,
I have a solaris machine we could throw up for the community as well
if required.
Sincerely,
Joshua Drake
Bruce Momjian wrote:
I signed up for an account, and it has already been helpful. I wish I
had known about this years ago. I will probably put together a little
sourceforge proj
On Fri, 10 Oct 2003 12:45 am, Bruce Momjian wrote:
> My gcc 2.95.3 manual says:
>
>-pipe Use pipes rather than temporary files for communi-
> [snip]
> so it looks like we can't use it on all platforms without testing. I
> will enable it for linux. Do people want to test other platforms?
Philip Yarra wrote:
> On Fri, 10 Oct 2003 12:45 am, Bruce Momjian wrote:
> > My gcc 2.95.3 manual says:
> >
> >-pipe Use pipes rather than temporary files for communi-
> > [snip]
> > so it looks like we can't use it on all platforms without testing. I
> > will enable it for linux. Do pe
I signed up for an account, and it has already been helpful. I wish I
had known about this years ago. I will probably put together a little
sourceforge project so I can get access to their Solaris and OS X
machines so I will have even better hardware access. Those are the only
two OS's missing
This has been saved for the 7.5 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
I know initdb might be in C for 7.5, but this behavior has to be ported
to 7.5 too then.
---
Andrew Dunstan wrote:
> Peter Ei
Where should I start on this? :-)
The implementation of postgres --help-config has several issues:
o it has options added "just in case someone ever need them"
o it has capital letters to negate, which we have never used
before
o uses GNU message reporting
Sean Chittenden wrote:
> > Oh, OK. I am on a dual, so maybe that's why I see an improvement.
> > If I can get another BSD guy to test this, I can remove the pipe for
> > all the BSD's.
>
> When benchmarking FreeBSD via worldstone, -pipe makes a difference
> (how much remains a debate). Since Post
Changed a couple of lines and traslated them in a better way.
Regards,
Fabrizio Mazzoni
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <[EMAIL PROTECTED]>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: PostgreSQL v7.4\n"
"POT-Creation-Date: 2003-10-05 13:25-0300\n"
"PO-Revision-Date: 2003-10-09 23:35
Fixed up alignment problems and improved some translations.
Regards,
Fabrizio Mazzoni
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <[EMAIL PROTECTED]>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: PostgreSQL v7.4\n"
"POT-Creation-Date: 2003-10-05 13:26-0300\n"
"PO-Revision-Date: 2003-10-09 23:58+
> Oh, OK. I am on a dual, so maybe that's why I see an improvement.
> If I can get another BSD guy to test this, I can remove the pipe for
> all the BSD's.
When benchmarking FreeBSD via worldstone, -pipe makes a difference
(how much remains a debate). Since PostgreSQL's compile is small
enough, i
On Thu, Oct 09, 2003 at 02:17:28PM -0400, Robert Treat wrote:
> Can you elaborate on "your purposes"? Do they fall into the
> "XA-compatibility" bit or the "Robustness in the face of network
> failure"?
Yes. I don't think that 2PC is a solution for robustness in face of
network failure. It's
On Thu, 9 Oct 2003, Peter Eisentraut wrote:
> I think we could allow users to set the transaction isolation level to
> READ UNCOMMITTED or REPEATABLE READ and internally behave like READ
> COMMITTED or SERIALIZABLE, respectively. The SQL standard seems to allow
> this:
Why not.
I would like a w
Added to TODO:
* Have VACUUM FULL use REINDEX rather than index vacuum
---
Alvaro Herrera wrote:
> On Sat, Oct 04, 2003 at 11:53:49PM -0400, Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
>
> > > Im
Bruce Momjian wrote:
> > The reason I'm waffling about whether the problem is completely fixed or
> > not is that the existing code will only remove-and-recycle completely
> > empty btree pages. As long as you have one key left on a page it will
> > stay there. So you could end up with ridiculous
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I think what Tom is concerned about is that this hasn't been tested
> > enough with big datasets. Also there a little loss of index pages but
> > it's much less (orders of magnitude, I think) than what was before.
> > This is because
This has been saved for the 7.5 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Andreas Joseph Krogh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This si my first look at the pg-code, s
Tom Lane wrote:
Josh Berkus <[EMAIL PROTECTED]> writes:
Now that we have Statement-level triggers, is there any reason we shouldn't
have triggers on SELECT?
Plenty, although I'm too tired to recall 'em all. The fundamental
problem with this is that it turns SELECT into an operation with
side-eff
Robert Treat wrote:
> On Tue, 2003-09-30 at 01:44, Christopher Kings-Lynne wrote:
> > * Mention that you might want to turn log_pid and log_timestamp off
> > since syslog logs them anyway
> >
>
> i think that debug_pretty_print is somewhat pointless too, as syslog
> tends to wrap lines automagic
Jan Wieck wrote:
> >> >My gcc 2.95.3 manual says:
> >> >
> >> >-pipe Use pipes rather than temporary files for communi-
> >> > cation between the various stages of compilation.
> >> > This fails to work on some systems where the assem-
> >> > bl
Bruce Momjian wrote:
Henry B. Hotz wrote:
>> Well, why do we have it enabled at all? If it's to speed compilation, we
>> may as well enable it on other platforms where -pipe works, of which
>> Linux is one.
>
>My gcc 2.95.3 manual says:
>
>-pipe Use pipes rather than temporary files fo
Joshua D. Drake wrote:
Hello,
I believe that the Int8/BigInt items are known issues but I have a
knew programmer that ran into it
over the weekend (he didn't call me when he encountered the problem,
when he should of) and we have a
customer that burned some significant time on it as well. Wil
On Thu, 2003-10-09 at 12:07, Andrew Sullivan wrote:
> On Thu, Oct 09, 2003 at 11:22:05AM -0400, Mike Mascari wrote:
> > The implementation choosen depends upon the answer, does it not? Is
> > there an implementation (e.g. 3PC) that can simulate 2PC behavior for
> > interoperability purposes and sat
Henry B. Hotz wrote:
> >> Well, why do we have it enabled at all? If it's to speed compilation, we
> >> may as well enable it on other platforms where -pipe works, of which
> >> Linux is one.
> >
> >My gcc 2.95.3 manual says:
> >
> >-pipe Use pipes rather than temporary files for commu
I think we could allow users to set the transaction isolation level to
READ UNCOMMITTED or REPEATABLE READ and internally behave like READ
COMMITTED or SERIALIZABLE, respectively. The SQL standard seems to allow
this:
[speaking about SET TRANSACTION]
5) The isolation level of TXN is set
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > > Well, why do we have it enabled at all? If it's to speed compilation, we
> > > may as well enable it on other platforms where -pipe works, of which
> > > Linux is one.
>
> On my (Linux) system, no -pipe is always faster than -pipe.
>
> > so
Bruce Momjian writes:
> > Well, why do we have it enabled at all? If it's to speed compilation, we
> > may as well enable it on other platforms where -pipe works, of which
> > Linux is one.
On my (Linux) system, no -pipe is always faster than -pipe.
> so it looks like we can't use it on all plat
Below is a short script which causes an error in the foreign key plan
caching. It appears to cause the error with or without the transaction,
but closing the connection between steps causes it to go away.
Can the cache be cleared after each statement?
Error reported:
psql:/home/rbt/bugte
On Thu, Oct 09, 2003 at 11:22:05AM -0400, Mike Mascari wrote:
> The implementation choosen depends upon the answer, does it not? Is
> there an implementation (e.g. 3PC) that can simulate 2PC behavior for
> interoperability purposes and satisfy both requirements?
I don't know. What I know is that
On Thu, 2003-10-09 at 11:14, Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > If you want cross-server transactions, what other methods are there that
> > are more reliable?
>
> 3-phase commit
How about a real world example of a transaction manager that has
actually implemented 3PC?
But ye
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > If you want cross-server transactions, what other methods are there that
> > are more reliable?
>
> 3-phase commit
OK, how is that going to make thing safer, or does it just shrink the
failure window smaller?
--
Bruce Momjian
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, next question is whether we should use _GNU_SOURCE only for plperl
> > compile, rather than everything. _GNU_SOURCE seems to do lots of stuff
> > that I am uncertain about.
>
> We've been using it for awhile, and it's not broken
Bruce Momjian wrote:
> Peter Eisentraut wrote:
>
>>Andrew Sullivan writes:
>>
>>>Does the proposal of allowing dbas to run that risk, provided there's a
>>>mechanism to tell them about it, satisfy the objection (assuming, of
>>>course, 2PC can be turned off)?
>>
>>Why would you spent time on impl
> > Why would you spent time on implementing a mechanism whose ultimate
> > benefit is supposed to be increasing reliability and performance, when you
> > already realize that it will have to lock up at the slightest sight of
> > trouble? There are better mechanisms out there that you can use ins
Bruce Momjian writes:
> If you want cross-server transactions, what other methods are there that
> are more reliable?
3-phase commit
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, next question is whether we should use _GNU_SOURCE only for plperl
> compile, rather than everything. _GNU_SOURCE seems to do lots of stuff
> that I am uncertain about.
We've been using it for awhile, and it's not broken anything. Why are
you so ea
On Thu, Oct 09, 2003 at 04:22:13PM +0200, Peter Eisentraut wrote:
> Why would you spent time on implementing a mechanism whose ultimate
> benefit is supposed to be increasing reliability and performance, when you
> already realize that it will have to lock up at the slightest sight of
> trouble? T
Neil Conway wrote:
> On Thu, 2003-10-09 at 09:35, Bruce Momjian wrote:
> > I only put back what was already there --- not sure why others don't use
> > it. You want it enabled on Linux?
>
> Well, why do we have it enabled at all? If it's to speed compilation, we
> may as well enable it on other p
Peter Eisentraut wrote:
> Andrew Sullivan writes:
>
> > Does the proposal of allowing dbas to run that risk, provided there's a
> > mechanism to tell them about it, satisfy the objection (assuming, of
> > course, 2PC can be turned off)?
>
> Why would you spent time on implementing a mechanism who
On Wed, Oct 08, 2003 at 02:31:29PM -0400, Bruce Momjian wrote:
> Well, this is really embarassing. I can't imagine why we would not set
> at least -O on all platforms. Looking at the template files, I see
> these have no optimization set:
I think gcc _used_ to generate bad code on SPARC if you s
Andrew Sullivan writes:
> Does the proposal of allowing dbas to run that risk, provided there's a
> mechanism to tell them about it, satisfy the objection (assuming, of
> course, 2PC can be turned off)?
Why would you spent time on implementing a mechanism whose ultimate
benefit is supposed to be
On Wed, Oct 08, 2003 at 05:43:49PM -0400, Bruce Momjian wrote:
>
> OK, I think we came to the conclusion that we want 2-phase commit, but
> want some way to mark a server as offline/read-only, or notify an
That sounds to me like the concusion, to the extent there was one,
yes. I'd still like to
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Do we want to try this approach that the DBD:pg guys are using?
> >
> > http://gborg.postgresql.org/pipermail/dbdpg-general/2003-September/000452.html
> >
> > It involves "$Config{q{ccflags}};". I think they can use it because
> > they are
Hans-Jürgen Schönig wrote:
> >>Stage 2) Parallel Postgres Servers, with the postmaster spawning off the
> >>server on a different node (possibly borrowing some code from GNU queue)
> >>and doing any buffer twiddling with RPC for that connection, The client
> >>connection would still be through t
DISCLAIMER: This message contains privileged and confidential information and is
intended only for the individual named.If you are not the intended
recipient you should not disseminate,distribute,store,print, copy or
deliver this message.Please notify the sender immediately by e-mail if
you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
If this isn't the right list for this type of question, please redirect
me to the relevant list.
I get the following error trying to restore a 7.2.2-dump-file in 7.4b4:
psql:nbeweb-db-as_copy-7.2.2.dmp:2051589: invalid command \nHelena
psql:nbeweb
Bruce Momjian writes:
> Do we want to try this approach that the DBD:pg guys are using?
>
> http://gborg.postgresql.org/pipermail/dbdpg-general/2003-September/000452.html
>
> It involves "$Config{q{ccflags}};". I think they can use it because
> they are using Makefile.PL, while our plperl i
The $Config-stuff is useable from the regular perl binary,
'perl -V:ccflags' for example.
-- Magnus
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
Do we want to try this approach that the DBD:pg guys are using?
http://gborg.po
70 matches
Mail list logo
