Decibel! írta:
On Mar 25, 2008, at 11:40 AM, Zoltan Boszormenyi wrote:
All of them? PostgreSQL allow multiple SERIALs to be present,
the standard allows only one IDENTITY column in a table.
And what about this case below?
CREATE TABLE t1 (id1 serial, ...);
ALTER SEQUENCE seq_t1_id1 RESTART WITH
The author has received feedback so this has been saved for the next
commit-fest:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Stephen Frost wrote:
-- Start of PGP signed section.
> * Dany DeBontridder (
On Wed, 02 Apr 2008 20:15:49 -0400
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> > I think it'd be especially cool if one could one-day have a command
> >
> > pg_install_module [modulename] -d [databasename]
> >
> > and it would magically get (or verify that it had) the latest
> > version from pgf
Andrew Dunstan wrote:
I think it'd be especially cool if one could one-day have a command
pg_install_module [modulename] -d [databasename]
Yes, and the CPAN analogy that has been in several minds, but it only
goes so far. Perl and Ruby are languages - Postgres is a very different
animal.
The author has been given feedback so this has been saved for the next
commit-fest:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Brendan Jurd wrote:
> On 31/03/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
>
Postgres does not backport features, so you would need to retrofit the
patch to 8.3 yourself, or pay / persuade somebody else to do that for
you. That should not be too hard, as it was in fact developed late in
the 8.3 cycle.
Before you jump on it as suiting your needs, read carefully. In
p
Based on recent patch feedback from Tom, this has been saved for the
next commit-fest:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Tom Lane wrote:
> "Sibte Abbas" <[EMAIL PROTECTED]> writes:
> > On 9/9/
It would be great help to me, and I am sure for many other people too who are
working with security solutions, if this feature is released as patch before
8.4 release.
Sanjay Sharma> Date: Tue, 1 Apr 2008 22:02:30 -0400> From: [EMAIL PROTECTED]>
To: [EMAIL PROTECTED]> CC: pgsql-hackers@postgr
Ron Mayer wrote:
Andrew Dunstan wrote:
Tom Lane wrote:
as having better system support for packages or modules or whatever
you want to call them; and maybe we also need some marketing-type
...re-raise the question of getting rid of contrib...
"The PostgreSQL Standard Modules".
While
Decibel! wrote:
> > I don't have any immediate ideas for improvement either, but we
> > certainly shouldn't consider this a totally solved problem.
>
> Something I always find myself wanting when debugging locking issues
> is what's in pg_locks. Could we save that information somewhere when
>
Andrew Dunstan wrote:
Tom Lane wrote:
as having better system support for packages or modules or whatever
you want to call them; and maybe we also need some marketing-type
...re-raise the question of getting rid of contrib...
"The PostgreSQL Standard Modules".
While renaming, could we g
Tom Lane wrote:
> For the past couple of weeks I've been dealing with both Bruce's queue
> and the one at
> http://wiki.postgresql.org/wiki/CommitFest:March
> and frankly I find the latter a *whole* lot more satisfactory, despite
> the fact that it's got exactly zero custom tooling or infrastructur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, April 02, 2008 17:49:49 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
> It doesn't, of course. What it does do is guarantee that the tarball
> matches the tag that has already been laid down in CVS.
'k, that was my thought, so usin
On Mar 25, 2008, at 11:33 AM, Sam Mason wrote:
On Mon, Mar 24, 2008 at 05:27:04PM -0500, Decibel! wrote:
On Mar 20, 2008, at 2:23 PM, Sam Mason wrote:
SELECT i, (MIN((j,k))).k
FROM tbl
GROUP BY i;
How is that any better than SELECT i, min(k) FROM tbl GROUP BY i ?
Because I want the value
I wrote:
> ... What I propose therefore
> is combining this patch with my older one so that ANALYZE counts
> according to the following rules:
> REDIRECT line pointer:ignore
> DEAD line pointer:count as dead
> HEAPTUPLE_LIVE tuple: count as live, include in stat
Magnus Hagander wrote:
> Was that really the conclusion? My memory of this thread showed that
> most people who actually deal with hashes and cryptography *wanted* a
> SHA based hash in core (because our users ask for it!) and the only
> disagreement was in *what* should be included.
Sorry if it l
On Mar 25, 2008, at 11:40 AM, Zoltan Boszormenyi wrote:
All of them? PostgreSQL allow multiple SERIALs to be present,
the standard allows only one IDENTITY column in a table.
And what about this case below?
CREATE TABLE t1 (id1 serial, ...);
ALTER SEQUENCE seq_t1_id1 RESTART WITH 5432 CYCLE;
or
On Mar 24, 2008, at 6:21 PM, Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Gregory Stark wrote:
The axis on which I still see real room for improvement here is
on the
description of the locks. It's awfully hard for a user to tell
from the
deadlock message exactly what operation
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> - --On Wednesday, April 02, 2008 18:08:05 +0200 Peter Eisentraut
> <[EMAIL PROTECTED]> wrote:
>> I believe we moved to using cvs export many years after 7.1. Before that,
>> the releases were made straight out of a cvs checkout. With cvs export i
Andrew Dunstan wrote:
If you have an alternative suggestion them you need to make it now.
well, I'm not sure about the non-collapsing business but no matter.
We are not intending to use FDs for message passing. They will be
stored in shared memory. See previous discussions for details:
I'm m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, April 02, 2008 18:08:05 +0200 Peter Eisentraut
<[EMAIL PROTECTED]> wrote:
> I believe we moved to using cvs export many years after 7.1. Before that,
> the releases were made straight out of a cvs checkout. With cvs export it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, April 02, 2008 12:33:24 -0400 Alvaro Herrera
<[EMAIL PROTECTED]> wrote:
> Peter Eisentraut wrote:
>> Am Mittwoch, 2. April 2008 schrieb Marc G. Fournier:
>> > Agreed ... but, stupid question here ... if our tags are wrong in CVS,
On Wed, Apr 02, 2008 at 05:09:14PM -0400, Andrew Dunstan wrote:
> Standard Modules". Maybe we could rename the directory "modules". IIRC
This seems like an easy and practical answer.
A
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Tom Lane wrote:
There is clearly work that could/should be done to improve it, such
as having better system support for packages or modules or whatever
you want to call them; and maybe we also need some marketing-type
work to encourage people such as hosting companies to allow access
to non-cor
Magnus Hagander <[EMAIL PROTECTED]> writes:
> ... These users would like to have sha1
> (and/or other securer hashes). And they would like it in -core, because
> their hosting company don't install the contrib modules.
That line of argument could be used to justify putting anything and
everything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, April 02, 2008 10:10:59 +0200 Magnus Hagander
<[EMAIL PROTECTED]> wrote:
> Could it be that a commit was done while the tag operation was running?
> Given that neither is an atomic operation in cvs, and it used to be
> that large
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Float is an approximate datatype. In this case, linux makes a fairly
> wild approximation (that it's the same as infinity) whereas windows
> says it just can't approximate it.
Note that the behavior isn't consistent across Unixen either ---
my HPUX box
Magnus Hagander wrote:
I think that claim is completely incorrect.
A lot of people use the md5() function in PostgreSQL today to hash
the passwords for the users of whatever webbapp they are running. It
only uses one account to connect to PostgreSQL and handles the rest of
the auth elsewhere in
"Pavan Deolasee" <[EMAIL PROTECTED]> writes:
> Please see the attached patch. One change I made is to hold the SHARE lock
> on the page while ANALYZE is reading tuples from it. I thought it would
> be a right thing to do instead of repeatedly acquiring/releasing the lock.
Bruce pointed out to me o
Was that really the conclusion? My memory of this thread showed that
most people who actually deal with hashes and cryptography *wanted* a
SHA based hash in core (because our users ask for it!) and the only
disagreement was in *what* should be included.
//Magnus
Bruce Momjian wrote:
>
> There is
Marc G. Fournier wrote:
> - --On Tuesday, April 01, 2008 14:06:09 -0400 Tom Lane
> <[EMAIL PROTECTED]> wrote:
>
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> >> In the meantime, does anyone have more information about how this
> >> came about?
> >
> > Marc's always done both the tagging and t
Tom Lane wrote:
> "Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> > I don't agree that we should just close discussion. Nobody seems
> > happy with the status quo, which is that we provide md5 but not
> > sha1,
>
> There may be a few people who are unhappy, but the above claim seems
> vastly o
Richard Wang wrote:
> I run the following sql statements in linux and get the results:
> postgres=# create table test_double(col1 float8);
> CREATE TABLE
> postgres=# insert into test_double values(1.7976931348623159E308);
> INSERT 0 1
> postgres=# select * from test_double;
>col1
> --
Tom Lane wrote:
For the past couple of weeks I've been dealing with both Bruce's queue
and the one at
http://wiki.postgresql.org/wiki/CommitFest:March
and frankly I find the latter a *whole* lot more satisfactory, despite
the fact that it's got exactly zero custom tooling or infrastructure
beh
James Mansion wrote:
Is the intent to replace most uses of (pg)kill with a general
purpose messaging system between the processes, or
(just) to address notify per se?
(Presumably with 'fire-and-forget' and also rpc
semantics? And pub-sub? And some sort of
write to an fd protected by an atomic
Greg Smith <[EMAIL PROTECTED]> writes:
> Those hacking on tools to convert Bruce's currently preferred working form
> (that revolves around mbox files) into something else that's web oriented
> are stuck with considering how all the above information is going to be
> handled before everybody wil
David Fetter wrote:
> And the cat's out of the bag there, too. Have you tried to get a
> system that doesn't include strong crypto running any time recently?
Well yes, I have recently been involved in a large deployment of such systems.
The details are a bit too involved for this thread, but th
Matthew Wetmore wrote:
Not sure if I posted in correct spot
pg_8.2.6
Centos5
Windows based app.
encryped pwd = yes
SSL = yes,
hostssl with explicit IP w/md5. (no pg_crypto)
We are in process of VISA CISP PCI compliance for our application.
(online cc auth - no stored cc data) [next pha
On Wed, 2 Apr 2008, Bruce Momjian wrote:
The new permanent ones are permanent against mailbox movement, and in
fact the comments and thread merging also travels with the email.
The "someone replied to your comment" links in e-messages I've been
getting the last few days have all been working,
Not sure if I posted in correct spot
But seems to be topic of today...funny on same day I hear from Visa.
pg_8.2.6
Centos5
Windows based app.
encryped pwd = yes
SSL = yes,
hostssl, with explicit IP w/md5,. (no pg_crypto)
This is just with client / server pwd auth
We are in process of VISA CI
Matthew Wetmore wrote:
> We just heard back today that they would like to use SHA1 for pwd auth.
Why would anyone want to do something so pointless?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-h
Not sure if I posted in correct spot
pg_8.2.6
Centos5
Windows based app.
encryped pwd = yes
SSL = yes,
hostssl with explicit IP w/md5. (no pg_crypto)
We are in process of VISA CISP PCI compliance for our application.
(online cc auth - no stored cc data) [next phase will include stored cc
d
Am Mittwoch, 2. April 2008 schrieb sanjay sharma:
> md5 is not being recommended anywhere because it contains hash collision.
> Therefore either it should be replaced with SHA1 or any other good hash
> algorithm or taken out of core completely. md5 in core is worthless now.I
> am not using it in my
On Wed, Apr 02, 2008 at 07:16:53PM +0200, Peter Eisentraut wrote:
> Am Mittwoch, 2. April 2008 schrieb David Fetter:
> > That cat is already out of the bag with every Linux distribution.
>
> There are other operating systems besides Linux.
And the cat's out of the bag there, too. Have you tried
sanjay sharma wrote:
Hi Tom,
md5 is not being recommended anywhere because it contains hash
collision. Therefore either it should be replaced with SHA1 or any
other good hash algorithm or taken out of core completely. md5 in core
is worthless now.I am not using it in my application. I am u
Am Mittwoch, 2. April 2008 schrieb David Fetter:
> That cat is already out of the bag with every Linux distribution.
There are other operating systems besides Linux.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.
The MAJOR benefit of Microsoft's approach is that it works on existing
application,
Yes, that is a nice benefit !
Is there a way to turn it on/off ? Or is it smart enough to only cache
plans for cases where it is relevant ?
For instance, I absolutely want some queries to be planne
sanjay sharma <[EMAIL PROTECTED]> writes:
> md5 is not being recommended anywhere because it contains hash
> collision.
For the purposes we are using it for, that's just about 100% irrelevant.
> Would replacing md5 with SHA1 in core involve much work?
Yes, it would be a tremendous problem, becau
David Fetter <[EMAIL PROTECTED]> writes:
> That cat is already out of the bag with every Linux distribution.
> There's just no point in our going three sides around the square in
> order to have someone, somewhere claim that our tarball isn't
> violating their law.
[shrug...] It's not exactly ter
On Wed, Apr 02, 2008 at 12:49:38PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > Re: compulsively attempting to comply with every law everywhere,
> > let's recall that a certain Search! engine company managed to get
> > itself in a morally pretty reprehensible spot by "follo
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> I believe we moved to using cvs export many years after 7.1. Before
>> that, the releases were made straight out of a cvs checkout. With
>> cvs export it is of course nearly impossible to create such a mess.
> Hmm, if we use
David Fetter <[EMAIL PROTECTED]> writes:
> Re: compulsively attempting to comply with every law everywhere, let's
> recall that a certain Search! engine company managed to get itself in
> a morally pretty reprehensible spot by "following the laws" of an
> oppressive regime. We needn't do the same.
David Fetter wrote:
On Wed, Apr 02, 2008 at 12:27:15PM -0400, Tom Lane wrote:
David Fetter <[EMAIL PROTECTED]> writes:
Just exactly which encryption legislation are we talking about
here?
I know there was some fuss about this issue back in the early
1990s, but that was many, man
Hi Tom,
md5 is not being recommended anywhere because it contains hash collision.
Therefore either it should be replaced with SHA1 or any other good hash
algorithm or taken out of core completely. md5 in core is worthless now.I am
not using it in my application. I am using SHA1 in client/web
Peter Eisentraut wrote:
> Am Mittwoch, 2. April 2008 schrieb Marc G. Fournier:
> > Agreed ... but, stupid question here ... if our tags are wrong in CVS, are
> > the 7.1.x releases themselves wrong too? When I do a release tarball, I
> > run:
> >
> > cvs -q export -rREL7_1_1 pgsql
>
> I believe w
On Wed, Apr 02, 2008 at 12:27:15PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > Just exactly which encryption legislation are we talking about
> > here?
>
> > I know there was some fuss about this issue back in the early
> > 1990s, but that was many, many law changes and c
David Fetter <[EMAIL PROTECTED]> writes:
> Just exactly which encryption legislation are we talking about here?
> I know there was some fuss about this issue back in the early 1990s,
> but that was many, many law changes and court cases ago, world-wide.
> It's far from clear to me that there's any
On Wed, Apr 02, 2008 at 01:07:01PM -, Greg Sabino Mullane wrote:
>
> > There isn't enough agreement to move some things from pgcrypto to
> > the core so this thread is being removed from the patch queue.
>
> I don't agree that we should just close discussion. Nobody seems
> happy with the sta
Am Mittwoch, 2. April 2008 schrieb Marc G. Fournier:
> Agreed ... but, stupid question here ... if our tags are wrong in CVS, are
> the 7.1.x releases themselves wrong too? When I do a release tarball, I
> run:
>
> cvs -q export -rREL7_1_1 pgsql
>
> so, if the tags are wrong, then all of those rel
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I don't think the wiki pages should be relying on Bruce's queue at all
>> --- they should just link into the mail archives.
> Except the comments are on my queue, and they are updated to join
> threads by adding comments to patches pos
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Upon verifying this I noticed that you broke all the permanent links the
> > other day, thus rendering both commitfest wiki pages useless -- just
> > fixed them. It would be nice that if you promise things to be
> > permanent, they a
The original patch author:
Chris Marcellino <[EMAIL PROTECTED]>
was not CC'ed as part of this email thread. That was a mistake. Chris,
the email thread discussing your patch is here:
http://archives.postgresql.org/pgsql-hackers/2008-03/msg01262.php
Please read the discussion -
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Upon verifying this I noticed that you broke all the permanent links the
> other day, thus rendering both commitfest wiki pages useless -- just
> fixed them. It would be nice that if you promise things to be
> permanent, they are really permanent. Othe
Alvaro Herrera wrote:
> Bruce Momjian escribi??:
> > Alvaro Herrera wrote:
>
> > > Upon verifying this I noticed that you broke all the permanent links the
> > > other day, thus rendering both commitfest wiki pages useless -- just
> > > fixed them. It would be nice that if you promise things to b
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> I don't agree that we should just close discussion. Nobody seems happy
> with the status quo, which is that we provide md5 but not sha1,
There may be a few people who are unhappy, but the above claim seems
vastly overblown. md5 is sufficient for
Bruce Momjian escribió:
> Alvaro Herrera wrote:
> > Upon verifying this I noticed that you broke all the permanent links the
> > other day, thus rendering both commitfest wiki pages useless -- just
> > fixed them. It would be nice that if you promise things to be
> > permanent, they are really p
Alvaro Herrera wrote:
> Bruce Momjian escribi??:
> >
> > Because of this:
> >
> > > variadic function, named params exist only as WIP and I see it for
> > > next commit fest. I'll send new version in next months.
> >
> > This has been saved for the next commit-fest:
> >
> > http://momjian.p
Bruce Momjian escribió:
>
> Because of this:
>
> > variadic function, named params exist only as WIP and I see it for
> > next commit fest. I'll send new version in next months.
>
> This has been saved for the next commit-fest:
>
> http://momjian.postgresql.org/cgi-bin/pgpatches_hold
Ye
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> There isn't enough agreement to move some things from pgcrypto
> to the core so this thread is being removed from the patch queue.
I don't agree that we should just close discussion. Nobody seems happy
with the status quo, which is that we pr
Le mardi 25 mars 2008, Dimitri Fontaine a écrit :
> postgres=# create index idx_prefix on ranges using gist(prefix
> gist_prefix_range_ops);
> NOTICE: gpr_picksplit(): entryvec->n= 234 maxoff= 232 l= 176 r= 56 l+r=
> 232 unionL='01[0-7]' unionR='01[4-7]'
> NOTICE: gpr_picksplit(): v->spl_ldatum=
On Wed, Apr 2, 2008 at 1:53 AM, Greg Smith <[EMAIL PROTECTED]> wrote:
> As far as the other more powerful machines you mentioned go, would need to
> know a bit more about the disks and disk controller in there to comment
> about whether those are worth the trouble to integrate. The big missing
>
If you look into documentation, the behavior of float/double is platform depend.
If you want to same result on any platform, use numeric instead.
Zdenek
Richard Wang napsal(a):
I run the following sql statements in linux and get the results:
postgres=# create table test_double
Hi Alvaro
On Fri, Mar 28, 2008 at 6:05 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> NikhilS escribió:
>
> > I will take a look at the pg_dump related changes if you want. We will
> need
> > changes in flagInhAttrs() and in getTableAttrs() to query the backend
> for
> > these 2 attributes for p
I run the following sql statements in linux and get the results:
postgres=# create table test_double(col1 float8);
CREATE TABLE
postgres=# insert into test_double values(1.7976931348623159E308);
INSERT 0 1
postgres=# select * from test_double;
col1
--
Infinity
(1 row)
but in windows:
p
74 matches
Mail list logo
