Hi
When will the bz2 (cygwin package release) be available?
Pieter
==
Download ringtones, logos and picture messages at Ananzi Mobile Fun.
http://www.ananzi.co.za/cgi-bin/goto.pl?mobile
---(end of broadcast)---
TIP 8: explain analyze is your frie
I get this in my logs from our backups. I ahve explicitly put -i in
pg_dumpall. How about we totally suppress this message if -i is supplied,
because obviously the person knows perfectly well it's proceeding despite
version mismatch?
Chris
pg_dump: server version: PostgreSQL 7.3.3 on i386-portb
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Tom> Personally I'd feel more comfortable with a shared-lock
Tom> approach, if we could work out the scalability issues. Dirty
Tom> reads seem ... well ... dirty.
Tom
I was going to do some experiments to measure the costs of our
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The issue I have is that every interface that relies on libpq is going
> to have to code it itself. Is that OK?
So? Most interfaces have to adhere to their own notions of transaction
semantics and control API anyway. libpq should stay out of their way
I just seem to recall a discussion where we decided to 'standardise' on
PostgreSQL...I'm not fussed tho.
Chris
- Original Message -
From: "Bruce Momjian" <[EMAIL PROTECTED]>
To: "Christopher Kings-Lynne" <[EMAIL PROTECTED]>
Cc: "Hackers" <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003
I see all submitted patches as applied, except from Gavin's WHERE
CURRENT OF patch, and I am asking for opinions on that one.
I will complete the release changes by Friday.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
Thomas liked Postgres rather than PostgreSQL in the docs, and I think
that's where it came from. I use Postgres in speaking, and PostgreSQL
in writing, so I guess either is OK.
---
Christopher Kings-Lynne wrote:
> Just a sl
The issue I have is that every interface that relies on libpq is going
to have to code it itself. Is that OK?
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Is there a reason autocommit is implemented i
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I was thinking of adding to TODO:
> > * Allow shared row locks for referential integrity
> > but how is that different from:
> > * Implement dirty reads and use them in RI triggers
>
> It'd be a completely different approach t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is there a reason autocommit is implemented in psql and not in libpq via
> a C function call?
One reason is that PQexec accepts multiple-query strings (possibly with
embedded BEGIN/END), so it's not immediately obvious what the semantics
ought to be. We
> Uh, the two big items are Win32 signal code, and reordering
> the startup code to allow exec without fork. Both are pretty
> complicated, but I do ask for assistance on the hackers list.
Ok. I guess we'll just keep our eyes peeled for the next time we can help
out.
Thanks for the replies...
Uh, the two big items are Win32 signal code, and reordering the startup
code to allow exec without fork. Both are pretty complicated, but I do
ask for assistance on the hackers list.
---
Claudio Natoli wrote:
>
> > I am al
Change made.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Should the new threading configure option be called:
> > --enable-thread-safeness
> > or
> > --enable-thread-safety
>
> safety is a c
OK, I checked the URL's, and I am a little confused. I don't understand
why the conditional transaction abort isn't in the same place as the
RESET ALL. Seems they should be done at the same time, though there is
an advantage to doing the RESET ALL during connect, because if someone
changes the p
Are you all done with the PHP persistent connection changes? Need any
help?
---
Marcus B?rger wrote:
> Hello Christopher,
>
> Wednesday, July 23, 2003, 6:49:05 AM, you wrote:
>
> >> > Surely PHP can be modified so as to
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I was thinking of adding to TODO:
> * Allow shared row locks for referential integrity
> but how is that different from:
> * Implement dirty reads and use them in RI triggers
It'd be a completely different approach to solving the FK locking
p
> I am already leading it, I think.
Ok. How do the willing get involved?
Cheers,
Claudio
---
WE HAVE MOVED - PLEASE NOTE OUR NEW CONTACT DETAILS:
THE BASEMENT, 33 EWELL STREET, BALMAIN NSW 2041
TEL: +61 2 9555 1544 FAX: +61 2 9555 6911
Certain disclaimers and policies apply to all email sen
I was thinking of adding to TODO:
* Allow shared row locks for referential integrity
but how is that different from:
* Implement dirty reads and use them in RI triggers
---
Tom Lane wrote:
> Rod T
Is there a reason autocommit is implemented in psql and not in libpq via
a C function call?
---
Bruce Momjian wrote:
> I see autocommit as implemented only in psql, not in libpq. Is that
> what we want to do for 7.4?
--
Someone at LinuxTag said they liked it because you can do the conversion
in a text file, rather than compiling a conversion C file.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Are we removing recode b
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Are we removing recode before going into beta?
I was waiting for someone to holler that they really want it, but so far
the silence is deafening ...
regards, tom lane
---(end of broadcast)
That's what I thought... just checking.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom, you saw this suggestion, right?
>
> I didn't hear anyone else agreeing with it ...
>
>
I am already leading it, I think.
---
Claudio Natoli wrote:
>
> Hi all,
>
> This probably more than a little premature/ill-timed, but I was hoping to
> start a groundswell of support for Win32 port.
>
> I, and I imagine q
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom, you saw this suggestion, right?
I didn't hear anyone else agreeing with it ...
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unr
Hi all,
This probably more than a little premature/ill-timed, but I was hoping to
start a groundswell of support for Win32 port.
I, and I imagine quite a number of capable lurkers on the list, would love
to get involved. Is there a way that work can be doled out now/soon, so that
we can make the
Tom, you saw this suggestion, right?
---
Bruce Momjian wrote:
> Bruce Momjian wrote:
> >
> > VERBOSE doesn't seem like the right name for the \set parameter. I
> > consider VERBOSE to be a possible value for error verbosit
Are we removing recode before going into beta?
---
Greg Stark wrote:
>
> Is recode a feature that's normally enabled?
>
> ./configure '--enable-recode' '--enable-integer-datetimes' '--enable-debug'
> '--with-perl' '--with
> > And if you can't find one that does what you want, ask for it.
> > The last thing we want is client-side code digging into those internal
> > representations --- we change 'em frequently.
>
> I want pg_get_* functions for every PostgreSQL object :P
And I want an easy way of parsing aclitem[]'s
> > Use the various pg_get_...() functions wherever you can.
>
> And if you can't find one that does what you want, ask for it.
> The last thing we want is client-side code digging into those internal
> representations --- we change 'em frequently.
I want pg_get_* functions for every PostgreSQL o
Why would someone not have the ability to read pg_user? The query is
gone in 7.4 anyway.
---
ivan wrote:
>
> in psql , file command.c : 1473 there is a query to check state for
> superuser, and this query is in begin/end t
Stuart wrote:
> Sorry for the tardiness in replying, I've been away for the past week or so.
> I didn't intend for 7.4 partly because I knew I'd be away & partly
> because I had seen there was a problem I hadn't realised with the
> previous patch and didn't want to submit something that may not b
Does anyone have any outstanding patches they expected would be applied
for 7.4? I think everything in my inbox has been dealt with, but I
might have missed something.
Bruce is not done generating release notes, so we probably will not have
a formal beta package ready until Friday. However, CVS
Peter, you have brought up some good items recently. Are you going to
handle them or do you want them added to the TODO list or 7.4 open items
list.
---
Peter Eisentraut wrote:
> In backend/commands/portalcmds.c we have
>
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> >>> Should we create some user-friendly macros for the error field codes?
>
> > I was actually talking of the single-letter codes that are used on the
> > protocol layer to tag the different fields of an error or notice result.
>
>
Bruce Momjian wrote:
> Andrew Sullivan wrote:
> > On Wed, Jul 30, 2003 at 12:38:54AM -0400, Bruce Momjian wrote:
> > > Guys, I just replied to this email on the BSDi email list. The issue is
> > > that someone found that some(most?) IDE drives have write cache enabled,
> > > though the drives
Just wondering if you shut down postmaster and restart, if the contents of
the file cache are written out to disk or still in the file cache. In
other words, will the number of transactions per second change if you shut
down postmaster and restart compared to restarting the machine
thanks
nailah
On Wednesday 30 July 2003 15:39, Bruce Momjian wrote:
> Andrew Sullivan wrote:
> > It's yet worse than this. Some IDE drives will respond to the
> > command to turn off write cacheing, but they _don't actually turn it
> > off_. In other words, you think you've done the right thing, and you
> > ha
Something similar to Linux's hdparm ?
http://www.google.com/search?q=hdparm%20bsd
-*- Bruce Momjian <[EMAIL PROTECTED]> [ 2003-07-30 19:41 ]:
> Andrew Sullivan wrote:
> > On Wed, Jul 30, 2003 at 12:38:54AM -0400, Bruce Momjian wrote:
> > > Guys, I just replied to this email on the BSDi email list
Andrew Sullivan wrote:
> On Wed, Jul 30, 2003 at 12:38:54AM -0400, Bruce Momjian wrote:
> > Guys, I just replied to this email on the BSDi email list. The issue is
> > that someone found that some(most?) IDE drives have write cache enabled,
> > though the drives do not preserve the write cache dat
Josh Berkus wrote:
> Guys:
>
> > That assumes we know what the shape of the log tables will be, but this
> > isn't quite clear to me - I can imagine it being different for different
> > needs. Having an external program to parse the logs into INSERT
> > statements would not be hard, anyway, so
I was thinking of outputing CREATE TABLE at the start of the log file.
I see what you mean that the schemas could be different, so we would
have to output the relevant fields all the time, like timestamp and
username, but because the username would be joined, you would only
output it on connectio
Guys:
> That assumes we know what the shape of the log tables will be, but this
> isn't quite clear to me - I can imagine it being different for different
> needs. Having an external program to parse the logs into INSERT
> statements would not be hard, anyway, so I'm not sure that this would
That assumes we know what the shape of the log tables will be, but this
isn't quite clear to me - I can imagine it being different for different
needs. Having an external program to parse the logs into INSERT
statements would not be hard, anyway, so I'm not sure that this would
buy us much. I'
One idea would be to output log information as INSERT statements, so we
could log connection/dbname/username to one table, and per-session
information to another table, and server-level info in a third table.
If you want to analyze the logs, you could load the data into a database
via inserts, an
Peter, I'm a little confused about the difference between the libdir and
pkglibdir settings created by configure. What's supposed to go where?
I got a complaint from a Red Hat person that the regression tests failed
on a 64-bit machine. Some investigation revealed that the problem was
that plpgs
On Wed, Jul 30, 2003 at 12:38:54AM -0400, Bruce Momjian wrote:
> Guys, I just replied to this email on the BSDi email list. The issue is
> that someone found that some(most?) IDE drives have write cache enabled,
> though the drives do not preserve the write cache data on power failure.
It's yet w
I said:
> It seems odd that the FATAL error is reported after, rather than before,
> the reconnection attempt; and it's really not acceptable to lose the
> PANIC message entirely.
Also, both classes of messages seem to be dropped if psql is not running
interactively (probably since it exits withou
The following test cases were created by modifying int4div and int2div
to produce FATAL and PANIC, respectively, instead of plain ERROR for
division-by-zero.
Using an older psql, all is well:
template1=# select 2/0;
FATAL: division by zero
server closed the connection unexpectedly
This p
On Tue, Jul 29, 2003 at 01:07:57PM +0200, Andreas Jung wrote:
>
> This problem appeard in 7.3.2 but it seems to have been fixed in 7.3.3.
> Our administrator complained that there has not been a notice in the
> CHANGELOG...so I am hestitating about choosing Postgres vs. Oracle :-)
I think your ad
There seem to be 2 orthogonal issues here - in effect how to log and
where to log. I had a brief look and providing an option to log the
dbname where appropriate seems to be quite easy - unless someone else is
already doing it I will look at it on the weekend. Assuming that were
done you could
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Going from precision 3 down to 0 - note the bug in (1). It always displays
> a trailing zero.
It's not a bug, it's a feature, or at least Tom Lockhart once thought so.
See TrimTrailingZeros() in datetime.c:
/* chop off trailing zeros...
Rod Taylor <[EMAIL PROTECTED]> writes:
> On Tue, 2003-07-29 at 21:45, Christopher Kings-Lynne wrote:
>> I hear that we're supposed to use the 'bin' versions of the 'src' columns
>> where possible. I would like then to use them in phpPgAdmin for displaying
>> defaults and stuff. Is there some way t
On Mon, 28 Jul 2003, Tom Lane wrote:
> Date: Mon, 28 Jul 2003 21:39:23 -0400
> From: Tom Lane <[EMAIL PROTECTED]>
> To: Robert Treat <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], Larry Rosenman <[EMAIL PROTECTED]>,
> Josh Berkus <[EMAIL PROTECTED]>,
> pgsql-hackers list <[EMAIL PROTECTED]
On Wed, Jul 30, 2003 at 12:38:54AM -0400, Bruce Momjian wrote:
>
> [ CC to Kurt and Steven on bsdi list.]
>
> Guys, I just replied to this email on the BSDi email list. The issue is
> that someone found that some(most?) IDE drives have write cache enabled,
> though the drives do not preserve the
54 matches
Mail list logo
