On Fri, Feb 6, 2009 at 5:45 PM, Euler Taveira de Oliveira
wrote:
> Alvaro Herrera escreveu:
>>> (ii) I think we should change the expression "storage parameters" for
>>> something else because autovacuum is related to maintenance. My suggestion
>>> is
>>> a general expression like "relation param
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > [ column privs cleanup patch ]
>
> Applied with revisions, as per previous messages.
Great, thanks!
Stephen
signature.asc
Description: Digital signature
Alvaro,
On the other hand, I'd been keen on a runtime suset autovaccum=on/off
which we could call from a cron job or the pgadmin scheduler in order to
have maintenance windows. Unless that's already becoming possible?
autovacuum=on/off is already SIGHUP as of 8.3 (not SUSET, since it makes
Alvaro Herrera escreveu:
>> (ii) I think we should change the expression "storage parameters" for
>> something else because autovacuum is related to maintenance. My suggestion is
>> a general expression like "relation parameters";
>
> I'm not sure I agree with this idea, because the term "storage
On Mon, 2009-01-19 at 21:41 +0300, Teodor Sigaev wrote:
> > gin_numeric_cmp() can be called from regular SQL. I missed this before,
> > but that function will segfault if you call gin_numeric_cmp(NULL, 1) (in
> > v0.7 at least).
>
> Fixed, gin_numeric_cmp is marked as strict.
>
> > And how does G
> diff -Nur ../cvs-pgsql/src/backend/utils/mb/wchar.c
> ./src/backend/utils/mb/wchar.c
> --- ../cvs-pgsql/src/backend/utils/mb/wchar.c 2009-01-30 10:35:27.0
> +0200
> +++ ./src/backend/utils/mb/wchar.c2009-02-06 18:19:48.0 +0200
> @@ -1373,6 +1373,7 @@
> {pg_latin12wchar
Stephen Frost writes:
> [ column privs cleanup patch ]
Applied with revisions, as per previous messages.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsq
On Wed, 2009-02-04 at 20:22 +0300, Teodor Sigaev wrote:
> > The description of extractQuery's extra_data parameter seems confusing
> > too. AFAICS it is incorrect, or at least misleading, to describe it as
> > void ** extra_data[]; it is really void ***extra_data, because there is
> > only one obj
Andrew Chernow wrote:
> Bruce Momjian wrote:
> > Andrew Chernow wrote:
> >> Andrew Chernow wrote:
> >>> Tom Lane wrote:
> Andrew Chernow writes:
> > I can try. Where should this be documented? ISTM that the best
> > place is at the top of "30.1 Database Connection Control Functions
On Feb 6, 2009, at 9:43 AM, Bruce Momjian wrote:
Oh. That seems kind of odd?can you hang onto the patch until 8.4 is
released, then? This must happen all the time, no?
OK, I will hang on to it, but I will have to mention it is only in 8.4
too.
Ah, yeah, I didn't put that in the patch…
Thank
Bruce Momjian wrote:
Andrew Chernow wrote:
Andrew Chernow wrote:
Tom Lane wrote:
Andrew Chernow writes:
I can try. Where should this be documented? ISTM that the best
place is at the top of "30.1 Database Connection Control Functions",
since the issue pertains to any connect/disconnect fu
Andrew Chernow wrote:
> Andrew Chernow wrote:
> > Tom Lane wrote:
> >> Andrew Chernow writes:
> >>> I can try. Where should this be documented? ISTM that the best
> >>> place is at the top of "30.1 Database Connection Control Functions",
> >>> since the issue pertains to any connect/disconnect
Ron Mayer wrote:
> Joshua D. Drake wrote:
> >> The main remaining use-case seems to me to make vacuuming work adhere
> >> to some business-determined schedule, hence maintenance windows seem
> >> like the next thing to do.
> > Also agreed.
>
> Somewhat agreed - since in many cases the business-de
On Fri, Feb 6, 2009 at 12:44 PM, Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> On Wednesday 14 January 2009 05:23:53 Tom Lane wrote:
>> > However, since there's no standard strftime escape for epoch,
>> > Robert's proposal to rip out the functionality would break any existing
>> > code that st
On Feb 6, 2009, at 9:12 AM, Bruce Momjian wrote:
Quick patch to mention CITEXT in the parts of the FAQ that discuss
case-insensitive comparisons.
I think it is too early to mention /contrib/citext in the FAQ because
8.4 is not released yet.
Oh, is the FAQ on the site built from CVS tip? Is t
Peter Eisentraut wrote:
> On Wednesday 14 January 2009 05:23:53 Tom Lane wrote:
> > However, since there's no standard strftime escape for epoch,
> > Robert's proposal to rip out the functionality would break any existing
> > code that still depends on this formatting option.
>
> If it came down t
David E. Wheeler wrote:
> On Feb 6, 2009, at 9:33 AM, Bruce Momjian wrote:
>
> >> Oh, is the FAQ on the site built from CVS tip? Is there not a branch
> >> for 8.3 from which it's built?
> >
> > There are FAQ's in each branch, but the one that is put on the web
> > site
> > is from CVS HEAD.
>
Joshua D. Drake wrote:
> On Thu, 2009-02-05 at 17:08 -0500, Tom Lane wrote:
>> My feeling is that we should be trying to eliminate use-cases for
>> cron-driven vacuuming, not trying to make sure that cron-driven
>> scripts can do anything autovacuum can.
> Agreed. IMO, the user should only have to
Euler Taveira de Oliveira escribió:
> (i) I don't like this construction "by entries by changing storage
> parameters". I prefer "by changing storage parameters" or "by entries in
> pg_class.reloptions";
Heh, obvious "by entries by" is a cut'n'pasto; fixed.
Maybe an xref would be better there.
Peter Eisentraut wrote:
Mykola Stryebkov wrote:
template1=# create database inf with encoding 'windows-1251';
WARNING: could not determine encoding for locale "uk_UA.KOI8-U":
codeset is "KOI8-U"
DETAIL: Please report this to .
CREATE DATABASE
template1=#
What's wrong with it?
PostgreSQL d
On Feb 6, 2009, at 9:12 AM, Bruce Momjian wrote:
Quick patch to mention CITEXT in the parts of the FAQ that discuss
case-insensitive comparisons.
I think it is too early to mention /contrib/citext in the FAQ because
8.4 is not released yet.
Oh, is the FAQ on the site built from CVS tip? Is t
On Feb 6, 2009, at 9:33 AM, Bruce Momjian wrote:
Oh, is the FAQ on the site built from CVS tip? Is there not a branch
for 8.3 from which it's built?
There are FAQ's in each branch, but the one that is put on the web
site
is from CVS HEAD.
Oh. That seems kind of odd…can you hang onto the p
David E. Wheeler wrote:
> On Feb 6, 2009, at 9:12 AM, Bruce Momjian wrote:
>
> >> Quick patch to mention CITEXT in the parts of the FAQ that discuss
> >> case-insensitive comparisons.
> >
> > I think it is too early to mention /contrib/citext in the FAQ because
> > 8.4 is not released yet.
>
> Oh
Josh Berkus wrote:
> I can't imagine, nor have I encountered in the 3 years of consulting I
> did since Autovaccum became available, such a use case.
Ok, so due to popular demand, I'm not implementing this new GUC.
> On the other hand, I'd been keen on a runtime suset autovaccum=on/off
> whi
Peter Eisentraut wrote:
> While regress/GNUmakefile appears to make an effort to run the regressions
> tests with or without locale depending on the users choice, .e.g.,
>
> # locale
> NOLOCALE =
> ifdef NO_LOCALE
> NOLOCALE += --no-locale
> endif
>
> the pg_regress.c implementation spoils that c
Tom Lane wrote:
> Alvaro Herrera writes:
> > Heikki Linnakangas wrote:
> >> Hmm, I remember I pondered for a long time if it should be COLLATE and
> >> CTYPE or LC_COLLATE and LC_CTYPE. I think the rationale in the end was
> >> that a) COLLATE/CTYPE looks nicer and b) if we add support for ICU
Tom Lane wrote:
> Log Message:
> ---
> Implement prefetching via posix_fadvise() for bitmap index scans. A new
> GUC variable effective_io_concurrency controls how many concurrent block
> prefetch requests will be issued.
>
> (The best way to handle this for plain index scans is still und
David E. Wheeler wrote:
> Quick patch to mention CITEXT in the parts of the FAQ that discuss
> case-insensitive comparisons.
I think it is too early to mention /contrib/citext in the FAQ because
8.4 is not released yet.
--
Bruce Momjian http://momjian.us
EnterpriseDB
Peter Eisentraut wrote:
> I have recently fixed the configure script to recognize Python 3.0. But
> note that building and running PL/Python with Python 3.0 does not
> actually work. It looks like several symbols have been removed or
> changed. It would be good if the Python pundits around he
Bruce Momjian writes:
> Robert Treat wrote:
>> I know that the fedora tzdata-2009a packages have the Argentian changes (as
>> well as some others depending on version of fedora), but I'm not sure what
>> is
>> includedin the original package, or exactly where we pull our changes in
>> from
>>
On Friday 06 February 2009 10:43:30 Bruce Momjian wrote:
> Bruce Momjian wrote:
> > Robert Treat wrote:
> > > I know that the fedora tzdata-2009a packages have the Argentian changes
> > > (as well as some others depending on version of fedora), but I'm not
> > > sure what is includedin the original
Bruce Momjian wrote:
> Robert Treat wrote:
> > I know that the fedora tzdata-2009a packages have the Argentian changes (as
> > well as some others depending on version of fedora), but I'm not sure what
> > is
> > includedin the original package, or exactly where we pull our changes in
> > from
Robert Treat wrote:
> I know that the fedora tzdata-2009a packages have the Argentian changes (as
> well as some others depending on version of fedora), but I'm not sure what is
> includedin the original package, or exactly where we pull our changes in from
> Note our release notes dont specify
Simon Riggs wrote:
All I'm saying is *if* we put scheduling inside Postgres for autovacuum
*then* we should make it general purpose scheduling.
If anybody uses the argument that "we have external schedulers, so don't
put them in the database" then that argument applies equally to
scheduling au
I know that the fedora tzdata-2009a packages have the Argentian changes (as
well as some others depending on version of fedora), but I'm not sure what is
includedin the original package, or exactly where we pull our changes in from
Note our release notes dont specify those changes, so I am incli
Hi Niranjan,
On Fri, Feb 6, 2009 at 6:46 PM, K, Niranjan (NSN - IN/Bangalore)
wrote:
> Hi,
>
>> Please retry new synch-rep code and report the following information.
>>
>> * server log
>> * /sbydata/walreceiver_trace.out
>> * tcpdump -i lo -n tcp
>>
>
> Refer attachments.
I'm afraid that the mes
Hi,
On Fri, Feb 6, 2009 at 2:14 PM, K, Niranjan (NSN - IN/Bangalore)
wrote:
> Hi,
>
>> * server log
>> * walreceiver_trace.out
>> * netstat -nap (before and after replication crashes)
>> * tcpdump -i lo -n tcp
>>
> In addition to the requested logs, I have provided the network interface
> informa
On Fri, 2009-02-06 at 10:06 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > On Thu, 2009-02-05 at 21:54 +0200, Heikki Linnakangas wrote:
> >> - If you perform a fast shutdown while startup process is waiting for
> >> the restore command, startup process sometimes throws a FATAL error
>
Simon Riggs wrote:
On Thu, 2009-02-05 at 21:54 +0200, Heikki Linnakangas wrote:
- If you perform a fast shutdown while startup process is waiting for
the restore command, startup process sometimes throws a FATAL error
which leads escalates into an immediate shutdown. That leads to
different me
39 matches
Mail list logo
