-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached is a patch that takes advantage of savepoints to enable
transactions to continue even after errors in psql. The name of it
is \reseterror, and it is off by default. It's backwards compatible,
and allows things like this to work on 8.0 and u
The attached dbsize patch:
+ makes relation_size(relname) include toast tables;
+ adds aggregate_relation_size(relname) to count table data and indices;
+ adds indices_size(relname) to report the size of indices for a
relation;
I've minimally tested it against PostgreSQL
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> Is it possible for one backend (with superuser privs) to release a lock
> held by anotether?
As of 8.0 this is not possible for regular locks, because there'd be no
way to update the other backend's internal data structure that shows
what locks it hol
Alvaro wrote:
> Please search this message in the archives:
right. heh. Well, moving on...
tgl wrote:
> Since subids and offnums are only 16 bits, we could pack all of these
> cases into 64 bits with a 16-bit type identifier to distinguish the
> cases. That would mean that LOCKTAG doesn't get an
On Tue, 25 Jan 2005, Andrew Dunstan wrote:
> ISTM that given how soundex-specific this function is it should have a
> less generic name than "difference".
>
> soundex_difference maybe?
>
Maybe, but difference is the name used by ms-sql, and it is also has
the same meaning in the ODBC/JDBC e
Korea PostgreSQL Users' Group wrote:
> diff -p nls.mk nls.mk.orig
Done.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Zhenbang Wei wrote:
> Thank you.
Does current mean 8.1 or 8.0?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Alin Vaida wrote:
> Unfortunately, this is the best I can come with right now :(
> I'll try to be more productive for the next release (I hope it won't
> be too soon, though).
Will appear in 8.0.1.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of b
"Matthew T. O'Connor" writes:
> Tom Lane wrote:
>> I was a bit worried about the scenario in which J Random Luser tries to
>> start the server twice and ends up with two autovacuum daemons attached
>> to the same postmaster. I'm not sure if this is possible, probable,
>> or dangerous ... but it s
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes:
> I resend the patch with diff -c.
What does XLOG_EXTRA_BUFFERS accomplish?
Also, I'm worried that you broke something by not updating
Write->curridx immediately in XLogWrite. There certainly isn't going
to be any measurable performance boost from kee
Tom Lane wrote:
"Matthew T. O'Connor" writes:
In the windows service world, is there any reason pg_autovacuum should
ever give up?
I was a bit worried about the scenario in which J Random Luser tries to
start the server twice and ends up with two autovacuum daemons attached
to the same po
Dear list
as you know there was a discussion in list about
using nls_string or nls_strxfrm function for having
multiple locale at the same time in postgresql.
many of developers accepted this method as a correct
but not perfect solution.
the main problem of this function is using setlocale
and
Kris Jurka wrote:
The attached patch implements the soundex difference function which
compares two strings' soundex values for similarity.
ISTM that given how soundex-specific this function is it should have a
less generic name than "difference".
soundex_difference maybe?
cheers
andrew
---
Excuse me.
I resend the patch with diff -c.
On Tue, 25 Jan 2005 10:30:01 +0100
"Michael Paesold" <[EMAIL PROTECTED]> wrote:
> ITAGAKI Takahiro wrote:
>
> > I think that there is room for improvement in WAL.
> > Here is a patch for it.
>
> I think you should resend your patch as a context diff
ITAGAKI Takahiro wrote:
I think that there is room for improvement in WAL.
Here is a patch for it.
I think you should resend your patch as a context diff (diff -c). Otherwise
it's hard to see what your patch does.
Best Regards,
Michael Paesold
---(end of broadcast)--
Hello, all.
I think that there is room for improvement in WAL.
Here is a patch for it.
- Multiple pages are written in one write() if it is contiguous.
- Add 'open_direct' to wal_sync_method.
WAL writer writes one page in one write(). This is not efficient
when wal_sync_method is 'open_sync'
Matthew T. O'Connor schrieb:
In the windows service world, is there any reason pg_autovacuum should
ever give up? The reason I had it give up was so that it didn't
accidently run against a different postgresql instance. I don't think
that will happen in the windows service world. I think it s
17 matches
Mail list logo
