Wayne Conrad wrote:
> the database started getting slow over time.
As Alvaro pointed out, this can happen if your fsm configuration
doesn't allow enough space for a normal VACUUM to keep track of all
the free space. Since you're running VACUUM with the VERBOSE option,
be sure to capture the ou
Interesting... it looks like there is a balance between CPU cycles and disk
I/O. I set the MAX_BRANCHES_TO_TEST to 120 and recompiled, so for me
everything is fast again. I do not know everything involved, but if there was
a way to flag the constraints used for partitioning and always check
The following bug has been logged online:
Bug reference: 4734
Logged by:
Email address: cerieljac...@gmail.com
PostgreSQL version: 8.3.7
Operating system: OS X 10.5.6
Description:warning: oosp/uuid.h: present but cannot be compiled
Details:
ossp-uuid = 1.6.2_0+univ
Wayne Conrad wrote:
> We started doing a routine VACUUM FULL ANALYZE on the advice of a
> friend after the database started getting slow over time. We did not
> realize that the FULL should never be done. We will change that to a
> VACUUM ANALYZE, without the full, and see how it goes.
>
> We d
On Wed, Mar 25, 2009 at 11:28:44AM -0400, Tom Lane wrote:
> What this looks like to me is an application problem. In each case
> you show, the only backends that actually *have* the lock are
> " in transaction", ie they are waiting for their clients to
> issue another command or close the transact
On Wed, Mar 25, 2009 at 09:15:48AM -0500, Kevin Grittner wrote:
> >>> "Wayne Conrad" wrote:
>
> > "VACUUM FULL ANALYZE VERBOSE" on a "deadlocks"
>
> > "VACUUM VERBOSE ANALYZE" (without the "FULL") does not
>
> You do realize that FULL should not be part of normal maintenance,
> right? It i
The following bug has been logged online:
Bug reference: 4733
Logged by: Daniel Miller
Email address: dan...@keystonewood.com
PostgreSQL version: 8.x
Operating system: N/A
Description:Feature request: add plpy.query_plan(...) to plpythonu
Details:
I have coded a fun
"Wayne Conrad" writes:
> "VACUUM FULL ANALYZE VERBOSE" on a "deadlocks" with other SQL statements.
What this looks like to me is an application problem. In each case
you show, the only backends that actually *have* the lock are
" in transaction", ie they are waiting for their clients to
issue an
On 3/25/09, Tom Lane wrote:
> "Ceriel Jacobs" writes:
> > ld: duplicate symbol _PGP_S2K_TYPE in pgp.o and pgp-mpi-openssl.o
>
> I think at bottom that's a compiler/linker bug which you should mention
> to Apple. However, I see what is causing it: pgp.h contains
>
> enum
> {
> PGP_S2
Marko Kreen writes:
> On 3/25/09, Tom Lane wrote:
>> Marko, am I right that this is just a syntax mistake, and not
>> intentional creation of a variable? There are several occurrences
>> of the pattern in pgp.h.
> Yes, it's syntax bug. Should I send patch?
No need, I think I can figure it out
>>> "Wayne Conrad" wrote:
> "VACUUM FULL ANALYZE VERBOSE" on a "deadlocks"
> "VACUUM VERBOSE ANALYZE" (without the "FULL") does not
You do realize that FULL should not be part of normal maintenance,
right? It is sometimes useful to recover from table bloat when normal
maintenance fails. A
"Ceriel Jacobs" writes:
> ld: duplicate symbol _PGP_S2K_TYPE in pgp.o and pgp-mpi-openssl.o
I think at bottom that's a compiler/linker bug which you should mention
to Apple. However, I see what is causing it: pgp.h contains
enum
{
PGP_S2K_SIMPLE = 0,
PGP_S2K_SALTED = 1,
On Tue, Mar 24, 2009 at 10:11 PM, Tom Lane wrote:
> Sigh ... I could've sworn I tested that code path, but evidently not,
> 'cause it's broken as can be.
If it's a code path not exercised by any regression test, is it worth
it to add one or we don't have any chance to break this code again
later?
Petrus wrote:
> The following bug has been logged online:
>
> Bug reference: 4732
> Logged by: Petrus
> Email address: peetupa...@hotmail.com
> PostgreSQL version: 8.2
> Operating system: dunno
> Description:Help me
> Details:
>
> Please Help me i forgot my old postg
The following bug has been logged online:
Bug reference: 4732
Logged by: Petrus
Email address: peetupa...@hotmail.com
PostgreSQL version: 8.2
Operating system: dunno
Description:Help me
Details:
Please Help me i forgot my old postgres password how i get it back??
-
The following bug has been logged online:
Bug reference: 4731
Logged by: Ceriel Jacobs
Email address: cerieljac...@gmail.com
PostgreSQL version: 8.3.7
Operating system: OS X 10.5.6
Description:compile with -fast fails on ld: duplicate symbol
_PGP_S2K_TYPE in pgp.o and
The following bug has been logged online:
Bug reference: 4730
Logged by: Wayne Conrad
Email address: wcon...@yagni.com
PostgreSQL version: 8.3.6
Operating system: Debian 4.3.1-1
Description:Vacuum full verbose analyze "deadlock"
Details:
"VACUUM FULL ANALYZE VERBOSE
Tom,
Thanks for the fix and the quick reply. Your patch solved my original
issue, as well as the supplied test case.
Regards,
Bruce Toll
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
18 matches
Mail list logo
