On Mon, Jul 10, 2006 at 02:03:11AM +0300, Tzahi Fadida wrote:
On Monday 10 July 2006 00:29, Martijn van Oosterhout wrote:
On Sun, Jul 09, 2006 at 10:08:42PM +0300, Tzahi Fadida wrote:
They return format_type_be(INT4OID) = integer or
format_type_be(FLOAT8OID) = double precision
I need
On Mon, Jul 10, 2006 at 01:04:09AM -0300, Marc G. Fournier wrote:
I, for one, would be interested in something like that ... somehow, this
'stripping' would have to be done within Majordomo2 itself, or ...
Leave pgsql-patches@ as an alias that is the stripper, with the end
result forwarded
Hello
I have problem with expressions:
select (select row(ret_num,ret_den) from mp.x_numer(39,32)) = row(32,33);
select mp.x_numer(39,32)) = row(32,33);
both has error:
ERROR: operator does not exist: record = record
LINE 1: ...lect row(ret_num,ret_den) from mp.x_numer(39,32)) = row(32,3...
Martjin, Greg, Marc, etc.:
However, I think the other suggestions of having the listbot mangle the
reply-tos of -patches and -committers to be -hackers would probably be
good too. I myself subscribe to -committers in digest form (where I
look at the summary to see if it's interesting) and read
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm not
exactly sure what to do with adddepends, though. It seems unlike to
lead an independant existance on pgFoundry; I'm inclined to just nuke it.
Now that the index options infrastructure is in, I am having a couple of
second thoughts about the specific behavior that's been implemented,
particularly for btree fillfactor.
1. The btree build code (nbtsort.c) is dependent on the assumption that
the fillfactor is at least 2/3rds. This is
Docs updated:
para
For schemas, allows the grantee to find objects contained in the
specified schema (assuming that the objects' own privilege requirements
are also met).
/para
---
Martijn
On Mon, Jul 10, 2006 at 12:36:34PM -0400, Tom Lane wrote:
Now that the index options infrastructure is in, I am having a couple of
second thoughts about the specific behavior that's been implemented,
particularly for btree fillfactor.
1. The btree build code (nbtsort.c) is dependent on the
Hi
I've now setup a warm-standby machine by using wal archiving. The
restore_command on the
warm-standby machine loops until the wal requested by postgres appears, instead
of
returning 1. Additionally, restore_command check for two special flag-files
abort
and take_online. If take_online
On Mon, Jul 10, 2006 at 12:49:54PM -0400, Bruce Momjian wrote:
Docs updated:
para
For schemas, allows the grantee to find objects contained in the
specified schema (assuming that the objects' own privilege requirements
are also met).
/para
I think that
Josh Berkus wrote:
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm not
exactly sure what to do with adddepends, though. It seems unlike to
lead an independent existence on pgFoundry; I'm
Ühel kenal päeval, E, 2006-07-10 kell 12:36, kirjutas Tom Lane:
3. What should the minimum fillfactor be? The patch as submitted
set the minimum to 50% for all relation types. I'm inclined to
think we should allow much lower fillfactors, maybe down to 10%.
A really low fillfactor could be a
On Mon, Jul 10, 2006 at 01:42:27PM -0400, Phil Frost wrote:
I think that misses the point. One can easily find objects in a schema
without usage by examining the system catalogs. The point is that there
are ways to access objects without going through the schema usage check,
and also that the
Hi Bruce,
In order to fix a win32 build error with thread safety enabled, can you
please move src/interfaces/libpq/pthread-win32.h to
src/include/port/win32/ ?
I've updated snake to build with thread safety enabled so hopefully this
won't go unnoticed if broken in the future.
Thanks, Dave.
On Mon, 10 Jul 2006, Bruce Momjian wrote:
Josh Berkus wrote:
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm not
exactly sure what to do with adddepends, though. It seems unlike to
lead
On Monday 10 July 2006 11:43, Gavin Sherry wrote:
On Mon, 10 Jul 2006, Bruce Momjian wrote:
Josh Berkus wrote:
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm
not exactly sure what to
Gavin Sherry wrote:
On Mon, 10 Jul 2006, Bruce Momjian wrote:
Josh Berkus wrote:
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm not
exactly sure what to do with adddepends, though.
On 7/10/06, Florian G. Pflug [EMAIL PROTECTED] wrote:
This methods seems to work, but it is neither particularly fool-proof nor
administrator friendly. It's not possible e.g. to reboot the slave without
postgres
abortint the recovery, and therefor processing all wals generated since the last
On Mon, Jul 10, 2006 at 08:24:08PM +0200, Martijn van Oosterhout wrote:
On Mon, Jul 10, 2006 at 01:42:27PM -0400, Phil Frost wrote:
I think that misses the point. One can easily find objects in a schema
without usage by examining the system catalogs. The point is that there
are ways to
Folks,
I was looking at migrating mSQL-interface to pgFoundry, but I'm not sure
there's any reason to do so. It was never finished, doesn't build, and
it's not like I run across mSQL databases in the field. Does anyone?
Shall we just kill it?
Also, tips is an apache log converter for which
Gavin,
There are still 7.2 systems out there which need it. The problem is,
adddepend is broken when run against 8.1. It breaks on serial, I think.
And on some other stuff, too. I didn't document all the failures, I
just tested and killed it.
Think is, 8.1 does a much better job of
On Mon, Jul 10, 2006 at 03:17:01PM -0400, Tom Lane wrote:
[EMAIL PROTECTED] writes:
... Do you think there should be a way of packing certain
indexes tighter, once they are known to be mostly read only? For
example, an option on REINDEX? This would free PostgreSQL to use a
smaller
Hi,
First, i use CTIDs to immensely speed up my function which is inherently slow
because of the problem itself.
I have a question about CTID invalidation when you open a read only cursor
using SPI. Why does it at all happens? Why is it so important to invalidate a
ctid of a read only query
[EMAIL PROTECTED] writes:
... Do you think there should be a way of packing certain
indexes tighter, once they are known to be mostly read only? For
example, an option on REINDEX? This would free PostgreSQL to use a
smaller fillfactor while still allowing people to optimize those of
their
Bruce Momjian wrote:
Josh Berkus wrote:
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm not
exactly sure what to do with adddepends, though. It seems unlike to
lead an independent existence
Josh Berkus wrote:
Folks,
I was looking at migrating mSQL-interface to pgFoundry, but I'm not sure
there's any reason to do so. It was never finished, doesn't build, and
it's not like I run across mSQL databases in the field. Does anyone?
Shall we just kill it?
Also, tips is an
On Mon, Jul 10, 2006 at 11:47:23PM +0300, Tzahi Fadida wrote:
Hi,
First, i use CTIDs to immensely speed up my function which is inherently slow
because of the problem itself.
I have a question about CTID invalidation when you open a read only cursor
using SPI. Why does it at all happens?
All,
At the request of Dave Page, here's the semi-final list after looking at
the code:
To be killed:
adddepends
tips
mSQL-interface
To be migrated to pgFoundry:
dbmirror (need owner)
dbase (owner?)
fulltextindex (owner?)
mac (LER)
On Tue, 2005-06-21 at 23:34 -0400, Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Tom Lane wrote:
In any case the correct way to solve the problem is to find out what's
being left corrupt by SIGTERM, rather than install more messiness in
order to avoid facing the real issue
Merlin Moncure wrote:
On 7/10/06, Florian G. Pflug [EMAIL PROTECTED] wrote:
This methods seems to work, but it is neither particularly fool-proof nor
administrator friendly. It's not possible e.g. to reboot the slave
without postgres
abortint the recovery, and therefor processing all wals
Marc,
You've lost me on that last point ... how does that save on spam filtering?
Many spam filters give points for reply-to address does not match from
address.
--Josh
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Mon, 10 Jul 2006, Josh Berkus wrote:
Martjin, Greg, Marc, etc.:
However, I think the other suggestions of having the listbot mangle the
reply-tos of -patches and -committers to be -hackers would probably be
good too. I myself subscribe to -committers in digest form (where I
look at the
On Mon, 10 Jul 2006, Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
On Sunday 09 July 2006 20:00, Greg Stark wrote:
BIRT pgsql-patches should be abolished in favour of something else that
accomplishes the bandwidth-reduction aspect without the downsides.
Alternatively, people
On Mon, Jul 10, 2006 at 11:22:49AM -0400, Josh Berkus wrote:
Folks,
For the code sprint, I'm starting off by removing the projects from
contrib which need to be removed by still have some usefulness. I'm
not exactly sure what to do with adddepends, though. It seems
unlike to lead an
On Tuesday 11 July 2006 00:35, Martijn van Oosterhout wrote:
On Mon, Jul 10, 2006 at 11:47:23PM +0300, Tzahi Fadida wrote:
Hi,
First, i use CTIDs to immensely speed up my function which is inherently
slow because of the problem itself.
I have a question about CTID invalidation when you
* Phil Frost ([EMAIL PROTECTED]) wrote:
I haven't found a way to do this yet, but I wouldn't be suprised if
there is a clever way, especially considering C extensions that might
come from contrib or other sources. It seems like there is a good deal
of potential for non-malicious developers to
Marc G. Fournier wrote:
On Mon, 10 Jul 2006, Josh Berkus wrote:
Martjin, Greg, Marc, etc.:
However, I think the other suggestions of having the listbot mangle the
reply-tos of -patches and -committers to be -hackers would probably be
good too. I myself subscribe to -committers in
1) Rod Taylor is not interested in maintaining it anymore;
2) It currently throws errors on 8.2 (and probably earlier);
3) With KL's improvements to pg_dump for 8.0, about half of its
functionality is no longer necessary.
So, speak up if someone thinks there's some reason to save adddepends
Think is, 8.1 does a much better job of upgrading 7.2 datatabases than
7.3 or 7.4 did anyway. I just tested using a database created in 7.1
and upgraded to 7.2 which has a baroque and unnecessarily complex schema
(legacy production applicaiton) which breaks on 7.4 without adddepends.
I was
Dear Hackers,
I would like to thank all of you for organizing, hosting, and attending
the 10th Anniversary PostgreSQL Conference last weekend. I was
especially interested in future PostgreSQL directions and that was
definitely the conference's theme. It was great to meet the community's
big
Martijn van Oosterhout kleptog@svana.org writes:
You're talking about invalidation as if it's something someone
deliberately does. That's incorrect. The t_ctid field is filled in if
and only if the tuple is exactly the on disk tuple. Otherwise it's a
new tuple, which by definition does not
41 matches
Mail list logo
