Marc G. Fournier wrote:
On Fri, 24 Mar 2006, Joel Miller wrote:
Joshua D. Drake wrote:
Is there any reason why we don't allow rsync access to the cvs repo?
The only reason I can possibly think of is server load, comparing the
timestamps for every file and directory in a repository for ever
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Just to be clear. The comma was a mistype. I was stating that you do not
want to use a period. If you use a period and you are not in the correct
directory, rsync will remove everything within your working directory.
Oh, so you're
I figure that Joshua just hit the wrong key ... or, at least, I hope
that is what he did, vs just going blind at a young age ;(
No, not that blind yet :)
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Just to be clear. The comma was a mistype. I was stating that you do not
> want to use a period. If you use a period and you are not in the correct
> directory, rsync will remove everything within your working directory.
Oh, so you're saying the s
On Sat, 25 Mar 2006, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Marc G. Fournier wrote:
/usr/local/bin/rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs .
its actually a "." ... what would a ',' do? :)
egad... heh... it would create a directory called "," ;) So y
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Marc G. Fournier wrote:
/usr/local/bin/rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs .
its actually a "." ... what would a ',' do? :)
egad... heh... it would create a directory called "," ;) So you probably
don't want
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Marc G. Fournier wrote:
>> /usr/local/bin/rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs .
>> its actually a "." ... what would a ',' do? :)
> egad... heh... it would create a directory called "," ;) So you probably
> don't want either.
U
Marc G. Fournier wrote:
On Fri, 24 Mar 2006, Joshua D. Drake wrote:
Marc G. Fournier wrote:
On Fri, 24 Mar 2006, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Is there any reason why we don't allow rsync access to the cvs repo?
That'd be Marc's bailiwick not mine ... but r
On Fri, 24 Mar 2006, Joshua D. Drake wrote:
Marc G. Fournier wrote:
On Fri, 24 Mar 2006, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Is there any reason why we don't allow rsync access to the cvs repo?
That'd be Marc's bailiwick not mine ... but rsync from the anoncvs
mir
Marc G. Fournier wrote:
On Fri, 24 Mar 2006, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Is there any reason why we don't allow rsync access to the cvs repo?
That'd be Marc's bailiwick not mine ... but rsync from the anoncvs
mirror seems like it couldn't pose any serious se
On Fri, 24 Mar 2006, Joel Miller wrote:
Joshua D. Drake wrote:
Is there any reason why we don't allow rsync access to the cvs repo?
The only reason I can possibly think of is server load, comparing the
timestamps for every file and directory in a repository for every rsync
session could be
On Fri, 24 Mar 2006, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Is there any reason why we don't allow rsync access to the cvs repo?
That'd be Marc's bailiwick not mine ... but rsync from the anoncvs
mirror seems like it couldn't pose any serious security threat.
Marc?
I
Joshua D. Drake wrote:
Is there any reason why we don't allow rsync access to the cvs repo?
The only reason I can possibly think of is server load, comparing the
timestamps for every file and directory in a repository for every rsync session
could be taxing if everyone under the sun and all
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Is there any reason why we don't allow rsync access to the cvs repo?
That'd be Marc's bailiwick not mine ... but rsync from the anoncvs
mirror seems like it couldn't pose any serious security threat.
Marc?
Well it would sure seem
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Is there any reason why we don't allow rsync access to the cvs repo?
That'd be Marc's bailiwick not mine ... but rsync from the anoncvs
mirror seems like it couldn't pose any serious security threat.
Marc?
regards, tom lane
Tom Lane wrote:
Neil Conway <[EMAIL PROTECTED]> writes:
I agree that investigating alternatives would be a good idea: AFAIK
there's no easy way to build cvsup on Linux/AMD64 (without patches and
more pain than I'm willing to endure), so I use cvsup on one machine and
then periodically rsync a c
This whole discussion reminds me why we've stuck so fervently to
bog-standard ANSI C for Postgres. There is a payoff for taking
portability seriously. Too bad the original authors of cvsup were more
interested in using a flavor-of-the-month programming language...
Is there any reason why we
Neil Conway <[EMAIL PROTECTED]> writes:
> I agree that investigating alternatives would be a good idea: AFAIK
> there's no easy way to build cvsup on Linux/AMD64 (without patches and
> more pain than I'm willing to endure), so I use cvsup on one machine and
> then periodically rsync a copy of that
On Thu, 2006-03-23 at 18:15 -0500, Tom Lane wrote:
> Personally, I'd really like to have a local repository copy, because
> I spend a *lot* of time with cvsweb etc --- but I'm sure my needs are
> several standard deviations away from the mean.
I'm actually amazed that anyone does any serious amoun
Josh Berkus writes:
> you missed one. Domains as parameters to functions are not
> enforced.
I think we've got that one actually. It's domains as PL-function output
types that aren't checked. Also plpgsql fails to enforce domain checks
on its local variables.
regards
Elein,
> Domains enable people to create basetype subtypes using SQL
> and procedural languages only. Current belief is that
> this "doesn't work." However, all of this has worked
> since domains were implemented with three exceptions.
you missed one. Domains as parameters to functions are no
On Fri, Mar 24, 2006 at 06:27:13PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Operators have the single distinction from functions in that when one
> > argument
> > has an unknown type, then an exact match is tried with the unknown arg
> > type set to the known type. This code
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > Eh, it does and it doesn't. The SQL standard says that no roles are
> > automatically inheirited and that you have to 'set role' to them.
> > Thus, all non-user roles which are granted to users in Postgres would
> > need to
elein <[EMAIL PROTECTED]> writes:
> Operators have the single distinction from functions in that when one argument
> has an unknown type, then an exact match is tried with the unknown arg
> type set to the known type. This code has always been in there.
Yeah, but it's just a fast special case of
Stephen Frost wrote:
> Eh, it does and it doesn't. The SQL standard says that no roles are
> automatically inheirited and that you have to 'set role' to them.
> Thus, all non-user roles which are granted to users in Postgres would
> need to be defined 'noinherit' to have things work as the spec w
On Fri, Mar 24, 2006 at 08:33:51PM +0100, Peter Eisentraut wrote:
> elein wrote:
> > Domains lay the groundwork for inherited basetypes
> > or subtypes.
>
> Semantically, a domain and a subtype are completely different things. A
> domain restricts the possible values of a type but behaves exactl
On Fri, Mar 24, 2006 at 03:47:13PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Attached is a patch to parse_oper.c which essentially does the
> > following. The major change is in binary_oper_exact().
> > Instead of checking only one level of the basetype it checks
> > all possi
To all the PostgresQL Developers,I just wanted to take a minute to say a very big thank you to everyone who has made PostgresQL the outstanding database that it is. I have been using it for more than 5 years now, and it has never ceased to amaze me just how stable, featureful and downright useable
Stephen Frost <[EMAIL PROTECTED]> writes:
> Eh, it does and it doesn't. The SQL standard says that no roles are
> automatically inheirited and that you have to 'set role' to them. Thus,
> all non-user roles which are granted to users in Postgres would need to
> be defined 'noinherit' to have thin
elein <[EMAIL PROTECTED]> writes:
> Attached is a patch to parse_oper.c which essentially does the
> following. The major change is in binary_oper_exact().
> Instead of checking only one level of the basetype it checks
> all possible combinations of type and parent types for
> an exact match (only
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > You were talking about 'enabled' vs. 'applicable' roles. Above
> > they're talking about 'enabled authorization identifiers' (the list
> > of roles you currently have the permissions of) and 'applicable
> > privileges' (the s
elein wrote:
> Domains lay the groundwork for inherited basetypes
> or subtypes.
Semantically, a domain and a subtype are completely different things. A
domain restricts the possible values of a type but behaves exactly like
that type in all other respects. (The fact that PostgreSQL allows you
Stephen Frost wrote:
> You were talking about 'enabled' vs. 'applicable' roles. Above
> they're talking about 'enabled authorization identifiers' (the list
> of roles you currently have the permissions of) and 'applicable
> privileges' (the specific privileges you have as that set of roles).
Acco
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > * Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> >> template1=3D# alter user foo rename to bar;
> >> NOTICE: MD5 password cleared because of role rename
>
> >> Now we have to reset the password.. which seems an ex
Background:
Domains lay the groundwork for inherited basetypes
or subtypes. By defining a domain and overriding
operators and possibly creating an operator class, then a domain
can be created which inherits the storage method
and all of the functions of a basetype. The domain
constraint enables
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > Well.. Applicable roles are roles which you can "SET ROLE" to, but
> > which you don't automatically get the permissions of (inherit). As I
> > recall, the spec wants all roles to be like this until an explicit
> > "SET ROLE
Stephen Frost wrote:
> Well.. Applicable roles are roles which you can "SET ROLE" to, but
> which you don't automatically get the permissions of (inherit). As I
> recall, the spec wants all roles to be like this until an explicit
> "SET ROLE" is done. When a "SET ROLE" is done, then that role (a
Stephen Frost <[EMAIL PROTECTED]> writes:
> * Joshua D. Drake ([EMAIL PROTECTED]) wrote:
>> template1=3D# alter user foo rename to bar;
>> NOTICE: MD5 password cleared because of role rename
>> Now we have to reset the password.. which seems an extra
>> step that shouldn't be required.
> Wouldn'
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> template1=# alter user foo rename to bar;
> NOTICE: MD5 password cleared because of role rename
> NOTICE: MD5 password cleared because of role rename
> ALTER ROLE
> template1=#
>
> Now we have to reset the password.. which seems an extra
> step that
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > Is there a particular issue/problem you're running into? It might
> > make more sense to focus on what you actually need than what the spec
> > says you need...
>
> The particular issue I'm running into is that I'm trying to
Hello,
Take the following:
template1=# alter user foo rename to bar;
NOTICE: MD5 password cleared because of role rename
NOTICE: MD5 password cleared because of role rename
ALTER ROLE
template1=#
Now we have to reset the password.. which seems an extra
step that shouldn't be required.
Joshua
Stephen Frost wrote:
> Is there a particular issue/problem you're running into? It might
> make more sense to focus on what you actually need than what the spec
> says you need...
The particular issue I'm running into is that I'm trying to get the
information schema up to speed but the current r
On Fri, Mar 24, 2006 at 08:54:54AM -0800, August Zajonc wrote:
> Martin,
>
> This would be extremely useful to have.
>
> For example, if I store currencies tagged properly, I could do a select
> and multiply the currency tag by the factor associated with that tag.
> This would allow easily quotin
Martijn van Oosterhout wrote:
> On Tue, Mar 21, 2006 at 03:59:31PM -0500, Andrew Dunstan wrote:
>>> I think such types would be better implemented as some sort of
>>> structured type, possibly with constructors and methods and all the
>>> other stuff that SQL talks about. We don't have all of th
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Davidson, Robert wrote:
>> If there were a place to download patches, this would allow moderately
>> adventurous Windows users to roll their own and avoid the overhead of
>> nightly Windows builds.
> ... you shouldn't need to apply patches directly, u
Davidson, Robert wrote:
I now have two minor bugs for which patches exist.
I am game to write up some better instructions for installing mingw to compile
postgresql on Windows if there are any notes on which packages need to be
installed. I have successfully compiled and installed on Linux.
On Fri, Mar 24, 2006 at 06:49:43AM -0800, Davidson, Robert wrote:
> I now have two minor bugs for which patches exist.
>
> I am game to write up some better instructions for installing mingw to
> compile postgresql on Windows if there are any notes on which packages need
> to be installed. I hav
I now have two minor bugs for which patches exist.
I am game to write up some better instructions for installing mingw to compile
postgresql on Windows if there are any notes on which packages need to be
installed. I have successfully compiled and installed on Linux.
If there were a place to do
On Fri, Mar 24, 2006 at 09:32:27AM -0500, Andrew Dunstan wrote:
> Jim C. Nasby wrote:
>
> >On Thu, Mar 23, 2006 at 05:30:28AM -0800, Davidson, Robert wrote:
> >
> >
> >>How amazing is that? I call it a night and come back to find that a bug
> >>has been identified and patched while I sleep.
> >>
Jim C. Nasby wrote:
On Thu, Mar 23, 2006 at 05:30:28AM -0800, Davidson, Robert wrote:
How amazing is that? I call it a night and come back to find that a bug has
been identified and patched while I sleep.
When will it appear in the binaries (I see that the release version is still
8.1.3)?
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> Trying to work in the new role features into the information schema, I
> noticed that there might be a few incompatibilities between the
> implementation and what the SQL standard would like to see.
This is true, and was discussed quite a bit about
On Mar 24, 2006, at 7:25 AM, Martijn van Oosterhout wrote:
Anyway, looking at the manpage of otool it doesn't say that it just
prints the raw name, so perhaps it's doing the same as ldd. To be sure
you'd need to strings the binary to see what it says.
Yes, strings shows the full path of prefi
Martijn van Oosterhout wrote:
On Fri, Mar 24, 2006 at 11:51:30AM +0100, Thomas Hallgren wrote:
Hi,
I'm currently investigating the feasibility of an alternative PL/Java
implementation that would use shared memory to communicate between a JVM
and the backend processes. I would very much like
On Thu, Mar 23, 2006 at 05:30:28AM -0800, Davidson, Robert wrote:
> How amazing is that? I call it a night and come back to find that a bug has
> been identified and patched while I sleep.
>
> When will it appear in the binaries (I see that the release version is still
> 8.1.3)? I thought about
On Fri, Mar 24, 2006 at 11:51:30AM +0100, Thomas Hallgren wrote:
> Hi,
> I'm currently investigating the feasibility of an alternative PL/Java
> implementation that would use shared memory to communicate between a JVM
> and the backend processes. I would very much like to make use of the
> routi
On Thu, Mar 23, 2006 at 07:47:13PM -0500, John DeSoi wrote:
>
> On Mar 23, 2006, at 12:15 AM, Tom Lane wrote:
>
> >OK ... it's supposed to work to shift the whole installation tree to
> >a new root, ie, paths to places like the /share and /lib directories
> >are determined relative to where the b
Hi,
I'm currently investigating the feasibility of an alternative PL/Java implementation that
would use shared memory to communicate between a JVM and the backend processes. I would very
much like to make use of the routines provided in shmem.c but I'm a bit uncertain how to add
a segment for m
On Fri, Mar 24, 2006 at 02:58:54PM +0800, Christopher Kings-Lynne wrote:
> >Yeah. AFAICS the transformation Chris suggested is valid. I'm really
> >dubious that it's worth expending planner cycles to look for it though.
> >LIKE is something that everybody and his brother uses, but who uses this
>
On Thu, Mar 23, 2006 at 06:35:58PM -0500, Rod Taylor wrote:
> On Thu, 2006-03-23 at 17:31 -0600, Tony Caduto wrote:
> > I could have swore that this worked in earlier releases of Postgresql
> > i.e. 7.4.
> >
> > CREATE TABLE public.test
> > (
> > junk double NOT NULL,
> > CONSTRAINT junk_pkey PRI
On Fri, Mar 24, 2006 at 07:54:09AM +0900, Satoshi Nagayasu wrote:
> Jim C. Nasby wrote:
> > Structure for the human-consumable output or for something that would be
> > machine-parsed? ISTM it would be best to keep the current output as-is,
> > and provide some other means for producing machine-fri
On 23/3/06 23:43, "Tony Caduto" <[EMAIL PROTECTED]> wrote:
> Peter Eisentraut wrote:
>> There has never been a type named double in PostgreSQL. The type name
>> mandated by the SQL standard is double precision, and PostgreSQL
>> supports that.
>>
>>
> Ok, Thanks for clearing that up for me
61 matches
Mail list logo
