Fujii Masao wrote:
On Thu, Dec 10, 2009 at 12:00 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The OS buffer is expected to be able to store a large number of
XLogRecPtr messages, because its size is small. So it's also OK
to just drop it.
It certainly seems to be something we could improve later,
I didn't really get any feedback on my proposal to add a new Discussing
review state to help out the reviewers and CF manager. To show how
adding it helps track the common flow of patches through the system, I
turned the whole CF into a big state machine and marked how the
transitions should
On tor, 2009-12-10 at 22:02 -0500, Robert Haas wrote:
On Thu, Dec 10, 2009 at 8:11 PM, Bruce Momjian br...@momjian.us wrote:
One idea would be to change the column _separator_ for newlines --- that
way, they don't show up for single-column output.
Hilariously enough, that's exactly what we
Hi,
Le 11 déc. 2009 à 01:43, Bruce Momjian a écrit :
Would you be up for writing the extension facility?
Uh, well, I need to help with the patch commit process at this point ---
if I find I have extra time, I could do it. I will keep this in mind.
If you ever find the time to do it, that
On Sat, Dec 12, 2009 at 02:41, Robert Haas robertmh...@gmail.com wrote:
On Sun, Dec 6, 2009 at 11:29 PM, Greg Smith g...@2ndquadrant.com wrote:
Magnus Hagander wrote:
On Sun, Nov 29, 2009 at 13:05, Magnus Hagander mag...@hagander.net wrote:
I'll be happy to work on this to get it ready for
On Sun, 2009-11-15 at 16:07 +0200, Heikki Linnakangas wrote:
- When replaying b-tree deletions, we currently wait out/cancel all
running (read-only) transactions. We take the ultra-conservative
stance because we don't know how recent the tuples being deleted are.
If we could store a better
KaiGai Kohei escribio':
Stephen Frost wrote:
Josh,
* Joshua Brindle (met...@manicmethod.com) wrote:
Stephen Frost wrote:
I do think that, technically, there's no reason we couldn't allow for
multiple only-more-restrictive models to be enabled and built in a
single binary
2009/12/12 KaiGai Kohei kai...@kaigai.gr.jp:
I'd like to summary about the framework.
I am not necessarily in agreement with many of the points listed in
this email.
* Functionalities
The ACE framework hosts both of the default PG checks and upcoming
enhanced securities. We can build a
(2009/12/12 15:42), Ing . Marcos Lui's Orti'z Valmaseda wrote:
KaiGai Kohei escribio':
Stephen Frost wrote:
Josh,
* Joshua Brindle (met...@manicmethod.com) wrote:
Stephen Frost wrote:
I do think that, technically, there's no reason we couldn't allow for
multiple only-more-restrictive
(2009/12/12 21:51), Robert Haas wrote:
2009/12/12 KaiGai Koheikai...@kaigai.gr.jp:
I'd like to summary about the framework.
I am not necessarily in agreement with many of the points listed in
this email.
* Functionalities
The ACE framework hosts both of the default PG checks and upcoming
I think I've found a better way of doing deferred conflict resolution
for WAL cleanup records. (This does not check for conflicts at block
level).
When a cleanup arrives, check *lock* conflicts to see who is accessing
the relation about to be cleaned.
If there are any lock conflicts, then wait,
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Changing the finish_time argument to pqWaitTimed into timeout_ms changes
the behavior connect_timeout option to PQconnectdb. It should wait for
max connect_timeout seconds in total, but now it is waiting for
connect_timeout seconds
I'm doing some work with the output of query_to_xml_and_xmlschema(). The
output is a bit unfortunate in my opinion when the column names in the
query are not legal XML names. We quite reasonably translate the names
so that legal XML names result, but we don't actually put the original
name
Andrew Dunstan and...@dunslane.net writes:
I propose that we annotate the schema section RowType elements with the
original names, so we would have something like this in the schema section:
1. Is that legal per the SQL/XML spec?
2. What happens when the column name contains characters that
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
I propose that we annotate the schema section RowType elements with the
original names, so we would have something like this in the schema section:
1. Is that legal per the SQL/XML spec?
It is certainly legal per XML
Using
http://www.postgresql.org/ftp/misc/winflex/
on a 64-bit windows, but in 32-bit mode (this certainly used to work),
trying to build HEAD.
first of all, it returns error code 128 when running flex -V, which
means our script claims it doesn't work. Commenting out that check, it
crashes along
The bitfromint8() and bitfromint4() are hosed. They produce wrong
results when the BIT size is more than 64 and 32 respectively, and the
BIT size is not multiple of 8, and the most significant byte of the
integer value is not 0x00 or 0xff.
For example:
test=# select (11::int423 |
* Robert Haas (robertmh...@gmail.com) wrote:
Allow me to assist- y is never in a structure once you're out of the
parser:
Well this is why you're writing the patch and not me. :-)
Sure, just trying to explain why your suggestion isn't quite the
direction that probably makes the most
* Tom Lane (t...@sss.pgh.pa.us) wrote:
Robert Haas robertmh...@gmail.com writes:
What exactly do you mean by a SubOID? I'm not really following that part.
I assume he's talking about the object reference representation used in
pg_depend, which is actually class OID + object OID +
Andrew Dunstan and...@dunslane.net writes:
Tom Lane wrote:
2. What happens when the column name contains characters that would have
to be escaped, such as --- haven't you just replaced one de-escaping
problem with another?
But the difference is that the XML processor will automatically
* Stephen Frost (sfr...@snowman.net) wrote:
* Tom Lane (t...@sss.pgh.pa.us) wrote:
I assume he's talking about the object reference representation used in
pg_depend, which is actually class OID + object OID + sub-object ID.
The only object type that has sub-objects at the moment is tables,
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
Tom Lane wrote:
2. What happens when the column name contains characters that would have
to be escaped, such as --- haven't you just replaced one de-escaping
problem with another?
But the difference is that the
Magnus Hagander wrote:
Using
http://www.postgresql.org/ftp/misc/winflex/
on a 64-bit windows, but in 32-bit mode (this certainly used to work),
trying to build HEAD.
first of all, it returns error code 128 when running flex -V, which
means our script claims it doesn't work. Commenting out
On Sat, Dec 12, 2009 at 21:19, Andrew Dunstan and...@dunslane.net wrote:
Magnus Hagander wrote:
Using
http://www.postgresql.org/ftp/misc/winflex/
on a 64-bit windows, but in 32-bit mode (this certainly used to work),
trying to build HEAD.
first of all, it returns error code 128 when
Greetings,
I'll start a new thread on this specific topic to hopefully pull out
anyone who's focus is more on that than on SEPG.
Row-Level security has been implemented in a number of existing
commercial databases. There exists an implementation of row-level
security for PostgreSQL today in
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Changing the finish_time argument to pqWaitTimed into timeout_ms changes
the behavior connect_timeout option to PQconnectdb. It should wait for
max connect_timeout seconds in total, but now it is waiting for
On Sat, Dec 12, 2009 at 12:24, Magnus Hagander mag...@hagander.net wrote:
On Sat, Dec 12, 2009 at 02:41, Robert Haas robertmh...@gmail.com wrote:
On Sun, Dec 6, 2009 at 11:29 PM, Greg Smith g...@2ndquadrant.com wrote:
Magnus Hagander wrote:
On Sun, Nov 29, 2009 at 13:05, Magnus Hagander
On lör, 2009-12-12 at 11:51 -0500, Andrew Dunstan wrote:
It is certainly legal per XML and XSD specs, and the SQL/XML spec has
annotations using appinfo elements. It would be rather surprising if
the
SQL/XML spec forbade annotations such as I propose. The spec is
mind-bogglingly
(2009/12/13 5:30), Stephen Frost wrote:
Greetings,
I'll start a new thread on this specific topic to hopefully pull out
anyone who's focus is more on that than on SEPG.
Row-Level security has been implemented in a number of existing
commercial databases. There exists an implementation of
Peter Eisentraut wrote:
On lör, 2009-12-12 at 11:51 -0500, Andrew Dunstan wrote:
It is certainly legal per XML and XSD specs, and the SQL/XML spec has
annotations using appinfo elements. It would be rather surprising if
the
SQL/XML spec forbade annotations such as I propose. The spec is
KaiGai,
* KaiGai Kohei (kai...@kaigai.gr.jp) wrote:
Please comment, update the wiki, let us know you're interested in this..
Good start, however, could you defer the discussion after the Feb-15?
My hands are now full in the security framework and SE-PgSQL/Lite. :(
While I'm glad you're
Stephen,
Please comment, update the wiki, let us know you're interested in this..
I blogged about this some time ago. One issue I can see is that I
believe that the RLS which many users want is different from the RLS
which SEPostgres implements.
Links:
KaiGai Kohei wrote:
What happens when
there is no entry in pg_largeobject_metadata for a specific row?
In this case, these rows become orphan.
So, I think we need to create an empty large object with same LOID on
pg_migrator. It makes an entry on pg_largeobject_metadata without
writing
Bruce Momjian wrote:
KaiGai Kohei wrote:
What happens when
there is no entry in pg_largeobject_metadata for a specific row?
In this case, these rows become orphan.
So, I think we need to create an empty large object with same LOID on
pg_migrator. It makes an entry on
(2009/12/13 10:39), Bruce Momjian wrote:
Bruce Momjian wrote:
KaiGai Kohei wrote:
What happens when
there is no entry in pg_largeobject_metadata for a specific row?
In this case, these rows become orphan.
So, I think we need to create an empty large object with same LOID on
pg_migrator. It
KaiGai Kohei wrote:
lo_import() has an another prototype which takes second argument to
specify LOID. Isn't it available to restore a large object with
correct LOID? For example, lo_import('/etc/profile', 1234)
I can't use that because the migration has already brought over the
pg_largeobject
Bruce Momjian wrote:
KaiGai Kohei wrote:
lo_import() has an another prototype which takes second argument to
specify LOID. Isn't it available to restore a large object with
correct LOID? For example, lo_import('/etc/profile', 1234)
I can't use that because the migration has already
On Sat, Dec 12, 2009 at 7:41 PM, Josh Berkus j...@agliodbs.com wrote:
Stephen,
Please comment, update the wiki, let us know you're interested in this..
I blogged about this some time ago. One issue I can see is that I
believe that the RLS which many users want is different from the RLS
(2009/12/13 11:31), Bruce Momjian wrote:
Bruce Momjian wrote:
KaiGai Kohei wrote:
lo_import() has an another prototype which takes second argument to
specify LOID. Isn't it available to restore a large object with
correct LOID? For example, lo_import('/etc/profile', 1234)
I can't use that
Magnus Hagander wrote:
On Sat, Dec 12, 2009 at 21:19, Andrew Dunstan and...@dunslane.net wrote:
Magnus Hagander wrote:
Using
http://www.postgresql.org/ftp/misc/winflex/
on a 64-bit windows, but in 32-bit mode (this certainly used to work),
trying to build HEAD.
first of all, it
On Thu, Dec 10, 2009 at 3:58 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Jaime Casanova escribió:
On Wed, Dec 9, 2009 at 9:39 AM, Tom Lane t...@sss.pgh.pa.us wrote:
so I'd like some independent confirmation that it does.
what kind of tests could show that? or simply running
41 matches
Mail list logo
