On Tuesday 30 June 2009 07:36:36 Itagaki Takahiro wrote:
> Header file "include/foreign/foreign.h" is not installed in 8.4.0.
>
> Did we forget to add subdir "foreign" to Makefile?
So it seems.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscri
Currently, the sigpipe-masking code in libpq is implemented as
a set of macros, which depend on declaring local variables.
This change adds a (private) struct sigpipe_info to contain the
compile-dependent data required for sigpipe masking and restoring.
The caller can then declare a struct sigpipe
Currently, libpq will wrap each send() call on the connection with
two system calls to mask SIGPIPEs. This results in 3 syscalls instead
of one, and (on Linux) can lead to high contention on the signal
mask locks in threaded apps.
We have a couple of other methods to avoid SIGPIPEs:
sockopt(SO_NOS
A new approach to avioding manipulating the signal mask during for every
send - this time round, use SO_NOSIGPIPE and MSG_NOSIGNAL if available.
The patches have been tested on Linux and OSX, and I've confirmed that
'struct foo { };' will compile with a MSVC compiler. I'd still like a
little more
> +1. Especially if I run it a few times and I can see
> which counters
> are still moving.
Per-node percentage is easy to do (given the perfect estimates, of course).
The problem comes when you want to give an "overall" percentage.
I wouldn't know where to put that "explain-like" output though
Now that 8.4.0 is out the door, development for 8.5devel will be opened any
day now. But we haven't discussed the development timeline so far. The core
team has several proposals:
CommitFest Alpha
Aug. 1 Sept. 1
Oct. 1 Nov. 1
Dec. 1 Jan ~~ 5
Feb. 1 Marc
Le 30 juin 2009 à 01:34, Greg Stark a écrit :
Basically I disagree that imperfect progress reports annoy users. I
think we can do better than reporting 250% done or having a percentage
that goes backward though. It would be quite tolerable (though perhaps
for no logical reason) to have a progres
Header file "include/foreign/foreign.h" is not installed in 8.4.0.
Did we forget to add subdir "foreign" to Makefile?
Index: src/include/Makefile
===
--- src/include/Makefile(8.4.0)
+++ src/include/Makefile(fixed)
@@
On Mon, Jun 29, 2009 at 10:22:15PM -0400, Robert Haas wrote:
> I'm finding myself unable to follow all the terminology on this thead.
> What's dimension reduction?
For instance, ask a bunch of people a bunch of survey questions, in hopes of
predicting some value (for instance, whether or not the
On Tue, Jun 30, 2009 at 4:39 AM, Josh Berkus wrote:
>
>
>> Well I don't understand how you get them wrong if you're just pasting
>> them from a file. I mean, sure you can pick the wrong template but
>> nothing can help you there. You could just as easily pick the wrong
>> template if it's a databas
On Tue, Jun 30, 2009 at 04:24:40AM +0100, Greg Stark wrote:
> On Tue, Jun 30, 2009 at 1:51 AM, Josh Berkus wrote:
> >
> >> It does seems slightly silly since surely anyone creating a new
> >> object would just paste in their grants from another object or
> >> some common source anyways, but I suppo
Greg,
Well I don't understand how you get them wrong if you're just pasting
them from a file. I mean, sure you can pick the wrong template but
nothing can help you there. You could just as easily pick the wrong
template if it's a database feature instead of a text file.
I really have to wonder
On Tue, Jun 30, 2009 at 1:51 AM, Josh Berkus wrote:
>
>>It does
>> seems slightly silly since surely anyone creating a new object would
>> just paste in their grants from another object or some common source
>> anyways, but I suppose that's the way with convenience features.
>
> That works fine unt
Tom Lane wrote:
> Bernd Helmle writes:
>> It might be interesting to dig into your proposal deeper in conjunction
>> with TOAST (you've already mentioned this TODO). Having serial access with
>> a nice interface into TOAST would be eliminating the need for
>> pg_largeobject completely (i'm not
On Mon, Jun 29, 2009 at 8:17 PM, Nathan Boley wrote:
> On Mon, Jun 29, 2009 at 3:43 PM, Tom Lane wrote:
>> David Fetter writes:
>>> On Mon, Jun 29, 2009 at 01:28:01PM -0700, Nathan Boley wrote:
... They dismiss
singular value decomposition and the discrete wavelet transform as
being
On Mon, Jun 29, 2009 at 4:53 AM, Bruce YUAN wrote:
> My function is to collect some backend information for user anlysis.
> How to register my function into backend? It make that we can called it via
> libpg/PQfn().
> Thanks!
I'm not sure this is -hackers question; seems like -general might be
mor
On Mon, Jun 29, 2009 at 8:15 PM, Ron Mayer wrote:
> Greg Stark wrote:
>>
>> Right, that was why my proposed interface was to dump out the explain
>> plan with the number of loops, row counts seen so far, and approximate
>> percentage progress.
>>
>> My thinking was that a human could interpret that
Hi All,
My function is to collect some backend information for user anlysis.
How to register my function into backend? It make that we can called it via
libpg/PQfn().
Thanks!
Best regards,
Bruce
Greg,
And there's "I just created a new table, I want "www" and
"www-backend" to get their usual privileges without thinking about it.
You want to be able to specify default grants that an object gets
based on the schema? That seems mostly reasonable though it might be a
good idea to have a WITH
On Mon, Jun 29, 2009 at 3:43 PM, Tom Lane wrote:
> David Fetter writes:
>> On Mon, Jun 29, 2009 at 01:28:01PM -0700, Nathan Boley wrote:
>>> ... They dismiss
>>> singular value decomposition and the discrete wavelet transform as
>>> being too parametric ( which is silly, IMHO )
>
>> Should we have
Greg Stark wrote:
Right, that was why my proposed interface was to dump out the explain
plan with the number of loops, row counts seen so far, and approximate
percentage progress.
My thinking was that a human could interpret that to understand where
the bottleneck is if, say you're still on the
>> Finally, this creates the partition but ( AFAICT ) it doesn't describe
>> a method for locating the histogram estimate given a point ( although
>> that doesn't seem too difficult ).
> Is that "not difficult," in terms of the math that needs doing, or
> "not difficult," in terms of how well Post
>> On Mon, 2009-06-29 at 14:07 -0400, Tom Lane wrote:
>>> I think this is pretty much nonsense --- most queries run all their plan
>>> nodes concurrently to some extent. You can't usefully say that a query
>>> is "on" some node, nor measure progress by whether some node is "done".
Right, that was
On Mon, Jun 29, 2009 at 9:02 PM, Josh Berkus wrote:
> What I'm saying is that there are many users currently using schema for
> security classes. I personally haven't ever encountered a DBA who used role
> ownership of objects as a mechanism for security context. There's nothing
> conceptually in
On Mon, Jun 29, 2009 at 06:43:35PM -0400, Tom Lane wrote:
> David Fetter writes:
> > On Mon, Jun 29, 2009 at 01:28:01PM -0700, Nathan Boley wrote:
> >> ... They dismiss singular value decomposition and the discrete
> >> wavelet transform as being too parametric ( which is silly, IMHO
> >> )
>
> >
Simon Riggs writes:
> On Mon, 2009-06-29 at 14:07 -0400, Tom Lane wrote:
>> I think this is pretty much nonsense --- most queries run all their plan
>> nodes concurrently to some extent. You can't usefully say that a query
>> is "on" some node, nor measure progress by whether some node is "done".
David Fetter writes:
> On Mon, Jun 29, 2009 at 01:28:01PM -0700, Nathan Boley wrote:
>> ... They dismiss
>> singular value decomposition and the discrete wavelet transform as
>> being too parametric ( which is silly, IMHO )
> Should we have a separate discussion about eigenvalues? Wavelets?
I t
On Mon, 2009-06-29 at 14:07 -0400, Tom Lane wrote:
> Josh Berkus writes:
> > So, while an actual % completed indicator would be perfect, a "query
> > steps completed, current step =" would still be very useful and a large
> > improvement over what we have now.
>
> I think this is pretty much n
2009/6/29 Ms swati chande
>
> Hi,
>
> I built postgresql from source using Windows 2005.
>
Did you read
http://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Native_Windows?
Why not use prebuilt versions (see
http://www.postgresql.org/download/windows)?
>
> After installation,
On Mon, Jun 29, 2009 at 01:28:01PM -0700, Nathan Boley wrote:
> > For things like PostGIS, which will want to index in 4 dimensions
> > (x, y, z, t), we might want to have multi-dimensional selectivity
> > histograms and some way to use same.
>
> Another use case is cross column statistics.
Good
> For things like PostGIS, which will want to index in 4 dimensions
> (x, y, z, t), we might want to have multi-dimensional selectivity
> histograms and some way to use same.
>
Another use case is cross column statistics.
> Anybody here qualified to check out this paper on the subject, please
> s
Greg,
In particular, one early question was whether to use wildcard patterns
or schema names. People were saying wildcard patterns would be more
flexible because people don't always set up their objects in different
schemas. But if we had a mechanism someone wanted to use which
depended on schem
On Mon, Jun 29, 2009 at 7:41 PM, Josh Berkus wrote:
> The main reason is existing practice.
I haven't followed the entire conversation so i'm not sure who I'm
going to be disagreeing with or agreeing with here. But I wanted to
mention that existing practice may not be a very useful place to start
Tom,
From what I recall of prior discussions, there is rough consensus that
the two types of facilities you mentioned (setting up default ACLs to be
applied at creation of objects created later, and providing a way to
change multiple objects' permissions with one GRANT) are desirable,
though th
Hi,
I built postgresql from source using Windows 2005.
After installation, I am trying to create a database using
createdb.
It then asks for a password. What password is it? There are now passwords set
on my system. Also tried editing pg_hba.conf. But could not solve the problem.
How do I mo
Thanks for your help.
It worked.
Regards
Swati
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Lars,
* Lars Kanis (ka...@comcard.de) wrote:
> The problem I have, is that I want to use an ordinary windows application,
> which connects to an arbitrary ODBC data source. This application stores a
> fixed username und password for the connection within it's own binary data
> file. It doesn't
Bernd Helmle writes:
> It might be interesting to dig into your proposal deeper in conjunction
> with TOAST (you've already mentioned this TODO). Having serial access with
> a nice interface into TOAST would be eliminating the need for
> pg_largeobject completely (i'm not a big fan of this one-
On Mon, Jun 29, 2009 at 1:07 PM, Tom Lane wrote:
> Josh Berkus writes:
>> So, while an actual % completed indicator would be perfect, a "query
>> steps completed, current step =" would still be very useful and a large
>> improvement over what we have now.
>
> I think this is pretty much nonsense -
Josh Berkus writes:
> The second, and bigger problem I can see is that this opens a whole new
> set of security holes by allowing an end-run around the existing access
> control structure with attackers can try to exploit.
Yeah. I'm very concerned about any scheme that invents additional
sourc
--On 29. Juni 2009 08:32:29 +0900 KaiGai Kohei wrote:
Yes, it intends to assign an identifier string not only numeric
large object identifier. The identifier string can be qualified
with a certain namespace as follows.
E.g)
SELECT lo_open('my_picture01', x'4'::int);
SELECT lo_create('p
Jeff,
I don't see why either of these things should be properties of the
schema. It seems to make much more sense for these defaults to be a
property of the user who creates the objects.
The main reason is existing practice. Currently, most applications I
see in the field which bother with h
Joshua Tolley writes:
> On Mon, Jun 29, 2009 at 02:07:23PM -0400, Tom Lane wrote:
>> I think this is pretty much nonsense --- most queries run all their plan
>> nodes concurrently to some extent. You can't usefully say that a query
>> is "on" some node, nor measure progress by whether some node i
Jeff Davis writes:
> On Mon, 2009-06-29 at 10:52 -0700, Josh Berkus wrote:
>> 1) ALTER SCHEMA SET DEFAULT PRIVILEGES statements which sets default
>> permissions, by ROLE and object type, on new objects.
>>
>> 2) a statement to set privs on all existing objects by type and role
>> within a sche
On Mon, Jun 29, 2009 at 02:07:23PM -0400, Tom Lane wrote:
> Josh Berkus writes:
> > So, while an actual % completed indicator would be perfect, a "query
> > steps completed, current step =" would still be very useful and a large
> > improvement over what we have now.
>
> I think this is pretty
On Mon, Jun 29, 2009 at 11:15 AM, wrote:
> So the code that I have right now works "pretty well" for the 10 queries of
> my project, but I guess won't work for general queries :(
I think that's probably right.
>> So, I'm all in favor of what you're trying to conceptually;
>> I just
>> don't lik
On Mon, 2009-06-29 at 10:52 -0700, Josh Berkus wrote:
> 1) ALTER SCHEMA SET DEFAULT PRIVILEGES statements which sets default
> permissions, by ROLE and object type, on new objects.
>
> 2) a statement to set privs on all existing objects by type and role
> within a schema.
I don't see why either
Josh Berkus writes:
> So, while an actual % completed indicator would be perfect, a "query
> steps completed, current step =" would still be very useful and a large
> improvement over what we have now.
I think this is pretty much nonsense --- most queries run all their plan
nodes concurrently t
All,
Actually, an indicator of even just what step of the query was being
executed would be very useful for checking on stuck queries. If a DBA
checks once that the query is on "bitmapscan on table_x(index_y)", and
it's still on that 15 minutes later, he/she can guess that the query is
thras
All,
First, let me talk about the problem: it's been my observation that the
majority of users, including public commercial web sites, which I run
into in the field do not employ permissions in any useful way to protect
their data. An awful lot of these applications are running as the
superu
Tom Lane wrote:
Mike Toews writes:
I have a few concerns with the usability and documentation for
pg_restore (note: I'm on 8.3, but I've checked the documentation for 8.4).
There's a TODO item about that already...
* Add support for multiple pg_restore -t options, like pg_dump
Jeff Davis wrote:
On Mon, 2009-06-29 at 12:55 -0400, Tom Lane wrote:
I think it has to be looked at in comparison to more general
prospective-permissions schemes;
When I searched google for "prospective permissions", all I found were
links to messages in this thread ;)
Can you refe
Mike Toews writes:
> I have a few concerns with the usability and documentation for
> pg_restore (note: I'm on 8.3, but I've checked the documentation for 8.4).
There's a TODO item about that already...
* Add support for multiple pg_restore -t options, like pg_dump
pg_restore's -t swit
Jeff Davis writes:
> Can you refer me to a general prospective-permissions scheme that is
> more widely accepted?
Well, the point of my post was that nothing's gotten to the point of
being "widely accepted". But there are people working on a "default
ACLs" scheme that would cover some of that te
Hey hackers,
I have a few concerns with the usability and documentation for
pg_restore (note: I'm on 8.3, but I've checked the documentation for 8.4).
In my attempts to restore a table (using -t) from a backup file with -v
(verbose) selected, I noticed a few things:
1. If a non-existent t
On Mon, 2009-06-29 at 12:55 -0400, Tom Lane wrote:
> I think it has to be looked at in comparison to more general
> prospective-permissions schemes;
When I searched google for "prospective permissions", all I found were
links to messages in this thread ;)
Can you refer me to a general prospectiv
Andrew Dunstan writes:
> David Fetter wrote:
>> There have been previous discussions of prospective permissions
>> changes. Are we restarting them here?
> It's not on the TODO list. I recall it being raised from time to time
> but I certainly don't recall a consensus that it should be done, nor
Folks,
For things like PostGIS, which will want to index in 4 dimensions
(x, y, z, t), we might want to have multi-dimensional selectivity
histograms and some way to use same.
Anybody here qualified to check out this paper on the subject, please
speak up :)
http://citeseerx.ist.psu.edu/viewdoc/s
> IMO
> any
> diagnostics you can provide for a low cost are
> useful. The more
> detail, the better. "Step 1 of 10" is good, "80%
> complete on step 1
> of 10" is better. "80% complete on step 1, 10%
> complete on 10 steps"
> is even better.
Well, I guess "Step 1 of 10" would be pretty trivi
Lars Kanis writes:
> The problem I have, is that I want to use an ordinary windows application,
> which connects to an arbitrary ODBC data source. This application stores a
> fixed username und password for the connection within it's own binary data
> file. It doesn't know anything about TLS-co
Am Montag, 29. Juni 2009 16:26:56 schrieben Sie:
> Lars Kanis writes:
> > this patch adds the possibility to map the login-rolename to a different
> > rolename actually used for permissions.
>
> This seems like an ugly addition with a very narrow use case. Can't
> you accomplish what you want wit
> It's
> easy to have
> estimates that are off by a factor of two or three, though,
> so I think
> you'd frequently have situations when the query completed
> when the
> progress estimater was at 40% or 250%.
I thought about implementing a "given perfect estimates" indicator at first
then, as a
Peter Eisentraut writes:
> On Monday 29 June 2009 17:20:09 Tom Lane wrote:
>> If it were
>> actually possible to support Win64 with only a couple of dozen lines
>> of changes, we would have done it long since.
> Possibly, or everyone was too confused and didn't know where to start.
Well, the pre
On Monday 29 June 2009 17:20:09 Tom Lane wrote:
> The problem with this is that it's barely the tip of the iceberg.
> One point I recall is that there are lots of places where "%lu" is
> assumed to be the correct format to print Datums with.
Hmm. I tried this out. typedef Datum to be long long
Lars Kanis writes:
> this patch adds the possibility to map the login-rolename to a different
> rolename actually used for permissions.
This seems like an ugly addition with a very narrow use case. Can't
you accomplish what you want with the existing usermap facility?
r
Tsutomu Yamada writes:
> Yes, I have read through the discusion but it seems somewhat faded
> out. This is because no platform other than Windows has 64bit
> pointer issues IMO. I think using intptr_t is cleaner and will bring
> more portability. Moreover it will solve Windows 64bit pointer issues
On Mon, Jun 29, 2009 at 4:47 AM, Scara Maccai wrote:
>> As to the content of the patch, I think that what you are doing is
>> comparing the actual number of "operations" with the expected number
>> of operations. If that's correct, I'm not sure it's really all that
>> useful, because it will only
On Mon, Jun 29, 2009 at 3:47 AM, Scara Maccai wrote:
>
> Is anyone interested in such a progress indicator???
>
I'm relatively new to Postgres and just starting to look at starting
to look at what we might do with it for handling large genomic
datasets. I've used Toad for Oracle to have a look at
Hi all,
this patch adds the possibility to map the login-rolename to a different
rolename actually used for permissions.
What is it used for?
I'm working with smartcard based TLS-authentication to connect to the PG
server. Authentication is done with the keys and certificates from the card
wi
Peter Eisentraut wrote:
Another thing we might want to consider once we have a robust extension
mechanism is to move some things out of the backend into extensions.
Candidates could be uuid, legacy geometry types, inet/cidr, for example.
These extensions would still be available and probabl
On Thursday 25 June 2009 01:09:17 Andrew Dunstan wrote:
> Well, I think in our case that would be going too far. I think there is
> a very good case for keeping a few key extensions in core both as
> exemplars and to make it easy to validate the extension mechanism
> itself. There have been suggest
Peter Eisentraut wrote:
> On Friday 26 June 2009 12:07:24 Tsutomu Yamada wrote:
> > Proposal: More portable way to support 64bit platforms
> >
> > Short description:
> >
> > Current PostgreSQL implementation has some portability issues to
> > support 64bit platforms: pointer calculations us
> You might want to take a look at this:
> http://wiki.postgresql.org/wiki/Submitting_a_Patch
I will; I'm sorry it wasn't in the proper format. It was just a proof of
concept, I guess I should have talked about it before even sending the patch.
> As to the content of the patch, I think that wh
73 matches
Mail list logo
