I have completed branding 7.4.3, and updated the release notes:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-7-4-3
Release is scheduled for Monday.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 35
I have been harping for the last few days (years, actually) about tweaks
and changes to PostgreSQL for a number of reasons ranging from session
management to static tables. I even had a notion to come up with msession
on PostgreSQL.
I have been incorporating full text search, recommendations, and
>>
>> Having been a Windows developer since version 1.03, with DOS
>> and CP/M before that, I can say with complete authority that
>> most Windows developers are not "good." The worst I've seen
>> is Charles Petzold, and he sets the bar.
>
> Charles Petzold is a decent programmer. I have read his
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>> It was done and we fixed a couple of bugs based on it (the
>> one I can think of offhand had to do with semantics of
>> aggregate functions in sub-selects). I don't think there's
>> anything more to be learned there.
> It is reassuring to know that
[EMAIL PROTECTED] wrote:
Actually, I am not a wide eyed passionate Linux zealot. Like my support
for John Kerry, I gladly choose the better side of mediocrity over extream
evil, it is nothing more than pure practicality.
I don't like dubya either, but he isn't extreme evil. This sort of
argum
On Fri, 2004-06-11 at 11:29, Dann Corbit wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Friday, June 11, 2004 9:39 AM
> > To: Tom Lane
> > Cc: Dann Corbit; Zeugswetter Andreas SB SD;
> > [EMAIL PROTECTED]; [EMAIL PROTECTED]; Bruce Momjian; Gr
On June 11, 2004 05:51 am, Christopher Kings-Lynne wrote:
> >>> 3. Or even create a pg_get_sequence() function:
> >>> SELECT SETVAL(pg_get_sequence(schema.table, col), 17);
> >>
> >> Actually, this is the best solution :)
>
> OK, attached is a pg_get_serial_sequence(schema, table, column) function
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 11, 2004 2:35 PM
> To: Dann Corbit
> Cc: Manfred Koizar; [EMAIL PROTECTED]
> Subject: Re: TESTING (was: RE: [HACKERS] More vacuum.c refactoring )
>
>
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
> >> ---
[EMAIL PROTECTED] wrote:
>
> >>
> >> We should provide people with the right tools, true, but we
> >> are bound by our conscience to inform them about Windows' failures.
> >
> > It must be nice to be young and still see everything as black and white
> > with no shades of gray.
>
> I wouldn't call
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>> --- and no I have zero confidence that passing the regression
>> tests proves anything, because all those prior bugs passed
>> the regression tests.
> Then why didn't those bugs get added to the regression?
Because there wasn't any reasonable way to
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 11, 2004 2:41 PM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]; PostgreSQL Win32 port list
> Subject: RE: [pgsql-hackers-win32] [HACKERS] Tablespaces
[snip]
> Microsoft has harmed the computing indust
>>
>> We should provide people with the right tools, true, but we
>> are bound by our conscience to inform them about Windows' failures.
>
> It must be nice to be young and still see everything as black and white
> with no shades of gray.
I wouldn't call 41 very young.
> For those who think that
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Thursday, June 10, 2004 2:19 PM
> To: Manfred Koizar
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] More vacuum.c refactoring
>
>
> Manfred Koizar <[EMAIL PROTECTED]> writes:
> > T
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 11, 2004 1:37 PM
> To: Dann Corbit
> Cc: Tom Lane; Zeugswetter Andreas SB SD;
> [EMAIL PROTECTED]; [EMAIL PROTECTED]; Bruce Momjian; Greg
> Stark; [EMAIL PROTECTED]; PostgreSQL Win32 port list
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Sent: Friday, June 11, 2004 9:39 AM
>> To: Tom Lane
>> Cc: Dann Corbit; Zeugswetter Andreas SB SD;
>> [EMAIL PROTECTED]; [EMAIL PROTECTED]; Bruce Momjian; Greg
>> Stark; [EMAIL PROTECTED]; PostgreSQL Win32 port li
> On Fri, Jun 11, 2004 at 11:51:04AM -0400, [EMAIL PROTECTED] wrote:
>
>> The best part of it could be that it could replace the whole msession C
>> API with PostgreSQL. You can join against the various data, and it
>> should
>> be very fast with no MVCC overhead for those aspects of your project
>
Tom Lane wrote:
This has got portability issues (fopen("ab"))
My doc says b is ignored on ansi systems, and recommends using it. Do
you have other experiences?
and I don't care for its
use of malloc in preference to palloc either.
Do we already have an applicable memory context in the postmast
Where are we on this?
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > One interesting idea would be for "SET include" to work like this:
> > SET include '/var/run/xx'
> > Notice there is no equals her
Tom Lane wrote:
> Andreas Pflug <[EMAIL PROTECTED]> writes:
> > The attached patch has the default filename issue fixed, and
> > documentation. Since I don't have a doc build system functional, there
> > might be tag mismatches or other typos; please check. IMHO this should
> > be committed with
Bruce Momjian wrote:
What is the recommended way to create mutex objects (CreateMutex) from
Win32 libraries? There must be a clean way like there is in pthreads.
It's having a central one-time called routine executing CreateMutex.
This can be DllMain, *if* used as DLL, but that's certainly no sol
Andreas Pflug wrote:
> Bruce Momjian wrote:
>
> >
> >What is the recommended way to create mutex objects (CreateMutex) from
> >Win32 libraries? There must be a clean way like there is in pthreads.
> >
>
> It's having a central one-time called routine executing CreateMutex.
> This can be DllMain
Andreas Pflug <[EMAIL PROTECTED]> writes:
> The attached patch has the default filename issue fixed, and
> documentation. Since I don't have a doc build system functional, there
> might be tag mismatches or other typos; please check. IMHO this should
> be committed without waiting for log rotati
On Fri, Jun 11, 2004 at 01:49:18PM -0400, Tom Lane wrote:
> Steve Atkins <[EMAIL PROTECTED]> writes:
> > Uhm... only updates within the current transaction. So if you merge the
> > global state and the local state that's exactly what you'll see.
>
> The only way this would work is if at every SetQ
Bruce Momjian wrote:
I was thinking of close/reopen so log files
could be rotated.
Log file rotation is fine, if we find a consensus quite soon how to
implement it... Seems as if I might find some time to implement it until
feature freeze.
The attached patch has the default filename issue fix
[ Thread moved to hackers and win32.]
Andreas Pflug wrote:
> Bruce Momjian wrote:
>
> >
> >
> >Agreed. My pthread book says pthread_mutex_init() should be called only
> >once, and we have to guarantee that. If the Windows implentation allows
> >it to be called multiple times, just create a fun
On Fri, Jun 11, 2004 at 11:51:04AM -0400, [EMAIL PROTECTED] wrote:
> The best part of it could be that it could replace the whole msession C
> API with PostgreSQL. You can join against the various data, and it should
> be very fast with no MVCC overhead for those aspects of your project that
> don
Steve Atkins <[EMAIL PROTECTED]> writes:
> Uhm... only updates within the current transaction. So if you merge the
> global state and the local state that's exactly what you'll see.
The only way this would work is if at every SetQuerySnapshot() you copy
*all* of the global variables as part of the
On Fri, 11 Jun 2004 14:11:00 +0200, Darko Prenosil
<[EMAIL PROTECTED]> wrote:
>I think I found bug related to table inheritance (or at least very weird
>behavior).
This is well known and there's a todo for it:
# Allow inherited tables to inherit index, UNIQUE constraint, and
primary key, foreig
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 11, 2004 9:39 AM
> To: Tom Lane
> Cc: Dann Corbit; Zeugswetter Andreas SB SD;
> [EMAIL PROTECTED]; [EMAIL PROTECTED]; Bruce Momjian; Greg
> Stark; [EMAIL PROTECTED]; PostgreSQL Win32 port list
>
On Fri, 2004-06-11 at 11:02, Bruce Momjian wrote:
> Gaetano Mendola wrote:
> [ PGP not available, raw data follows ]
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Bruce Momjian wrote:
> >
> > | Gaetano Mendola wrote:
> > |
> > |>Bruce Momjian wrote:
> > |>
> > |> > I understand yo
Gaetano Mendola wrote:
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruce Momjian wrote:
>
> | Gaetano Mendola wrote:
> |
> |>Bruce Momjian wrote:
> |>
> |> > I understand your points below. However, the group has weighed in the
> |> > direction o
On Fri, Jun 11, 2004 at 12:17:57PM -0400, Greg Stark wrote:
> Steve Atkins <[EMAIL PROTECTED]> writes:
>
> > So, if you take a local snapshot of the global at the beginning of
> > your transaction then the visible changes at any point are those from
> > transactions that commited before your trans
Steve Atkins <[EMAIL PROTECTED]> writes:
> So, if you take a local snapshot of the global at the beginning of
> your transaction then the visible changes at any point are those from
> transactions that commited before your transaction started. That's
> well-defined, at least, and appears to be pr
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
>> I expect that one year after release, there will be ten times as many
>> PostgreSQL systems on Win32 as all combined versions now on UNIX flavors
>
> I surely hope not. Especially not multi-gig databases. The folks
> running those should know better
> I don't think we want features for their own sake, though, and I'm
> not convinced that raw filesystems are actually useful. Course, it's
> not my itch, and PostgreSQL _is_ free software.
>
I agree that raw file systems are seldom useful with one caveat, more
advanced file systems are sometime
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> e.g if you have a constraint "acol integer, check acol < 5"
> and you have a query with a "where acol = 10" you could reduce that
> to "where false".
I think part of the question is how much work do you put into checking this.
Checking c
As you may or may not be aware, I've been sort of ranting about high speed
frequently updated tables the last few days. Sorry if I've annoyed anyone.
It occured to me last night that PostgreSQL's recent capability of
returning sets of rows from functions was a feature that a long abandoned
project
On Fri, Jun 11, 2004 at 09:27:07AM +0100, Richard Huxton wrote:
> >If the transaction is rolled back, the local state variable is
> >thrown away. If the transaction is commited and the local state
> >variable has been invalidated then the global state variable is
> >invalidated, otherwise the glob
[snip]
I've been harping on this problem myself the last couple days.
A summary table with frequent vacuums is your best bet for the existing
versions of PostgreSQL. It is, IMHO, suboptimal, but a workable solution
depending on the expected database load.
Right now I am exploring the possibility
3. Or even create a pg_get_sequence() function:
SELECT SETVAL(pg_get_sequence(schema.table, col), 17);
Actually, this is the best solution :)
OK, attached is a pg_get_serial_sequence(schema, table, column) function
. I have tested it with crazy names and it seems to be good. It works
like this
I think I found bug related to table inheritance (or at least very weird
behavior).
Here is simplified example:
DROP SCHEMA master CASCADE;
DROP SCHEMA skladisno CASCADE;
CREATE SCHEMA master;
CREATE SCHEMA skladisno;
CREATE TABLE master.analiticki_subje
This is not a viable solution, as oid's are not guaranteed to be unique,
nor are they primary keys; finally tables can be created without oid's,
in fact AFAIK, this will be the default in 7.5.
Dave
On Fri, 2004-03-05 at 08:25, Rudolpho Gian-Franco Gugliotta wrote:
> Hi,
>
> i'm using the jdbc pos
> > With the rule system and two underlying tables one could make it work by
> > hand I think.
>
> The rule system could be used to do this, but there was some discussion of
> using inherited tables to handle it. However neither handles the really hard
> part of detecting queries that use only a
Tom Lane wrote:
"Dann Corbit" <[EMAIL PROTECTED]> writes:
I expect that one year after release, there will be ten times as many
PostgreSQL systems on Win32 as all combined versions now on UNIX flavors
I surely hope not. Especially not multi-gig databases. The folks
running those should kn
Steve Atkins wrote:
Stop me if you've heard this before.
I'm looking at fast calculation of aggregates (sum(), max(), count())
across large tables, or across fairly simply defined subsets of those
tables.
Lets say that, for a given aggregate function on a given table (with a
given where clause, per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruce Momjian wrote:
| Gaetano Mendola wrote:
|
|>Bruce Momjian wrote:
|>
|> > I understand your points below. However, the group has weighed in the
|> > direction of clearly showing non-default values and not duplicating
|> > documentation. We can ch
Stop me if you've heard this before.
I'm looking at fast calculation of aggregates (sum(), max(), count())
across large tables, or across fairly simply defined subsets of those
tables.
Lets say that, for a given aggregate function on a given table (with a
given where clause, perhaps), each postg
On Tue, Jun 01, 2004 at 06:40:07PM -0400, Bruce Momjian wrote:
> When "DELETE a" happens, we remove the xmin=1 from the tuple header and
> replace it with xmin=3. xid=3 will be marked as committed if xid2
> aborts, and will be marked as aborted if xid3 commits.
>
> So, if xid2 aborts, the insert
48 matches
Mail list logo
