the cause might be? Or better still, how to fix it? :)
Thanks,
- Mark
Vmware: {root} % /usr/local/bin/perl Makefile.PL
Configuring DBD::Pg 2.13.1
PostgreSQL version: 80307 (default port: 5432)
POSTGRES_HOME: /usr/local/PostgreSQL
POSTGRES_INCLUDE: /usr/local/PostgreSQL/include
POSTGRES_LIB: /usr/l
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: vrijdag 1 mei 2009 16:37
To: Craig Ringer
Cc: Mark; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Unable to make DBD-Pg-2.13.1
Craig Ringer writes:
>> Mark wrote:
>>> Until I tried to install DBD-Pg-2
-Original Message-
From: pgsql-bugs-ow...@postgresql.org
[mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
Sent: vrijdag 1 mei 2009 17:46
To: Mark Kramer
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4787: Hardlink (ln) causes startup failure with
bizarre
-Original Message-
From: pgsql-bugs-ow...@postgresql.org
[mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
Sent: vrijdag 1 mei 2009 23:57
To: Mark; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4787: Hardlink (ln) causes startup failure with
bizarre
On Sat, 02 May 2009 14:47:48 GMT, Tom Lane wrote
> Mark writes:
> > I understand the rationale for relocatable packages. So,
> > I guess hardlinks are out. But, barring hardlinks,
> > perhaps, in the existence of a symlink, a simple 'readlink'
> > f
Test platform = Win 2000 plus all service packs, hotfixes.
No previous PostgreSQL ever installed on the machine before.
8.0.0 beta 5 installation executable from
http://pgfoundry.org/projects/pginstaller
Installed NOT AS A SERVICE, repeat NOT as a WinNT/2K service.
Told installer to put installat
The following bug has been logged online:
Bug reference: 5851
Logged by: Mark
Email address: dvlh...@gmail.com
PostgreSQL version: 9.0.2 x86_64
Operating system: CentOS release 5.5 (Final) | 2.6.18-194.17.1.el5 #1 SMP
X86_64
Description:ROHS (read only hot standby
urately ? (or a
value that high isn't be accepted?)
I have reloaded configs and still seeing 0's
I assume you would suggest I turn that number down... a lot.
..: Mark
> -Original Message-
> From: Robert Haas [mailto:robertmh...@gmail.com]
> Sent: Friday, Januar
> -Original Message-
> From: Robert Haas [mailto:robertmh...@gmail.com]
> Sent: Sunday, January 30, 2011 12:19 PM
> To: mark
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #5851: ROHS (read only hot standby) needs to be
> restarted manually in somecases
On Sun, Jan 30, 2011 at 12:45 PM, mark wrote:
>
>
>> -Original Message-
>> From: Robert Haas [mailto:robertmh...@gmail.com]
>> Sent: Sunday, January 30, 2011 12:19 PM
>> To: mark
>> Cc: pgsql-bugs@postgresql.org
>> Subject: Re: [BUGS] BUG #5851
> -Original Message-
> From: Fujii Masao [mailto:masao.fu...@gmail.com]
> Sent: Tuesday, February 08, 2011 4:00 PM
> To: mark
> Cc: Robert Haas; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #5851: ROHS (read only hot standby) needs to be
> restarted manually
> -Original Message-
> From: Robert Haas [mailto:robertmh...@gmail.com]
> Sent: Thursday, March 03, 2011 9:04 AM
> To: mark
> Cc: Fujii Masao; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #5851: ROHS (read only hot standby) needs to be
> restarted manually
The following bug has been logged online:
Bug reference: 6029
Logged by: mark
Email address: m...@remidata.com
PostgreSQL version: 9.0.2
Operating system: RHEL 6.0 x86_64
Description:packaged installer fails to configure ldap
Details:
The source code installation
indefinitely if the transactions
never complete due to pooler issues.)
Expected behavior would be -T would mean a hard cut off.
Thoughts ?
-Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
'm not sure
that counts as cloud-like in its architecture...
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 4584
Logged by: Mark Muzenhardt
Email address: mark.muzenha...@arcor.de
PostgreSQL version: 8.3.5-2
Operating system: Windows XP professional
Description:PostgreSQL service doesn't start
Details:
I
The following bug has been logged online:
Bug reference: 4612
Logged by: Mark Hayen
Email address: mark.ha...@atosorigin.com
PostgreSQL version: 8.3.5
Operating system: Ubuntu 8.10
Description:lc_numeric setting ignored
Details:
When setting the LC_NUMERIC to
He Bruce,
Thank you for replying.
Does this mean that there is no way to do a "\copy from" using CSV files
containing decimals with
a comma?
Mark Hayen
ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n
g e h e i m e i n f o r m a t i e b e v a t t e n
The following bug has been logged online:
Bug reference: 4787
Logged by: Mark Kramer
Email address: r...@asarian-host.net
PostgreSQL version: 8.3.7
Operating system: FreeBSD 7.1
Description:Hardlink (ln) causes startup failure with bizarre
"timezone_abbrevia
eration program for this
dataset if required.
regards
Mark
cursor-bug.tar.gz
Description: GNU Zip compressed data
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
three-line patch. The question of how cursors should behave with
respect to volatile functions can be documented and left for another
time.
Sounds like a good approach.
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.post
The following bug has been logged online:
Bug reference: 5031
Logged by: Mark Douglas
Email address: m...@steelhousemedia.com
PostgreSQL version: 8.4.0
Operating system: Ubunto Linux
Description:DATE_TRUNC returns the wrong value when specifying MONTH
Details:
The
I have my timezone set to GMT so there really shouldn't be any time zone
adjustments.
Mark
On 9/2/09 10:01 PM, "Tom Lane" wrote:
"Mark Douglas" writes:
> The following use of DATE_TRUNC returns the wrong value. I called the
> function on 2009-09-02. It sho
You're correct. When I run this from psql it returns the correct result. When I
run it from DBVisualizer, which I normally use, it adjust the result to my
local time zone. Thanks for looking into it. Sorry about bugging you with that.
Thanks,
Mark
On 9/2/09 10:24 PM, "Tom Lane"
sult[0] . "\n");
reproduces what Yujin is seeing, whereas replacing $sql with:
$sql = "SELECT false::int4";
gives a 0 in the result array. I guess it must be something funny with
how PDO represents the bool type...(will have a look at the PDI code).
But this needs to be raised
Mark Kirkwood wrote:
I guess it must be something funny with how PDO represents the bool
type...(will have a look at the PDO code). But this needs to be raised
on bugs.php.net.
FYI - a related bug is : http://bugs.php.net/bug.php?id=33876
--
Sent via pgsql-bugs mailing list (pgsql-bugs
sql
version of this example returns a string "0" from PDO, so gives a 0 for
false in a more expected/intuitive way...
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
t include where gatenforce lives.
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
oper
subset, is countable and hence has Lebesgue measure zero on the real
line.
;)
LOL - fortunately (going by the bug) he is not trying to compute a
measure (i.e integrate) from a set of 'em.
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to you
not allow one customer to impact
others.
That's it for now.
Hope someone can provide helpful answers.
Thanks,
Mark W.
What is the most ideal/optimal platform for postgresql? Linux
(distro?), freebsd, windows, etc.
consider memory management, file system performance, threading model
etc.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgre
= 0;
}
echo 'Cur Id: ',$curId,"\n";
Running this code it hangs after echoing 'Rolling back', but only hangs
every other execution (assuming the sequence was deleted first).
I think you need to be using $pdo->exec instead of $pdo->query for
everythi
cally 'postgres' to eliminate this
possibility.
With respect to the libpq source, it is in the source tarball from the
Postgresql website (directory src/interfaces/libpq ).
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes t
ld produce different answers.
I suspect they do not. Its all in the permissions.
Cheers
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
obert suggested, try
doing 'SELECT user' in both.
Also note that Pgadmin user PQexec and PQgetValue...
Cheers
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
:
DELETE FROM b WHERE id = 1;
The record from table a disappears, but the record in table b is still
there. Of course this is a very stupid construction, but I would expect some
kind of error / warning message instead. Now it is possible to corrupt your
data.
Best regards,
Mark Kazemier
e you using pgAdmin? If so, just right-click on the database and
select "delete/drop".
Probably too late to be mentioning this... but Daniel, are you sure that
the database is not needed by anything?
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
Your name :Mark Kirkwood
Your email address :[EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) :Intel Pentuim
Operating System (example: Linux 2.0.26 ELF) :Linux 2.2.14-5.0 ELF
(Redhat 6.2)
PostgreSQL
-linux-gnu, compiled by gcc 2.96
I'm sure if what I tried is even valid input, but I'm guessing this is
not a desired result in any case. :)
Thanks for the great software and good luck with this!
A frequent Postgres user,
-mark
personal website } Sum
---
|| | ||
| |
(1 row)
#
It returns a row with a null shipment id!
I'm not sure what's happening here-- I tried to simplify this to a
simple case, but I couldn't reproduce t
, so perhaps my
oddity would be repaired anyway. Thanks for checking it out.
-mark
http://mark.stosberg.com/
Tom Lane wrote:
>
> Mark Stosberg <[EMAIL PROTECTED]> writes:
> >I'm running Postgres 7.0.2 and have run into a curious situation. I
> > got a back a nu
o be returned as the result. I can work
around
this by including an extra step to make sure that my data is not null
before
it's passed off a SQL statement like this.
Thanks!
-mark
http://mark.stosberg.com/
---(end of broadcast)---
T
I'll give it a shot and post the patch or let you know I'm stuck. :) Thanks!
-mark
Tom Lane wrote:
>
> Mark Stosberg <[EMAIL PROTECTED]> writes:
> > * Install earthdistance operator from the contrib directory.
> > * try this:
> > cascade=> select
> Tom Lane wrote:
> >
> > Mark Stosberg <[EMAIL PROTECTED]> writes:
> > > * Install earthdistance operator from the contrib directory.
> > > * try this:
> > > cascade=> select null <@> '1,1'::point;
> >
> > >
rts -b -Fc core4 > core4.dump
gives these errors when trying to restore
pg_restore: [archiver (db)] could not execute query: ERROR: insert_fsm_page_entry:
failed to insert entry!
and
ERROR: insert_fsm_page_entry: failed to insert entry!
in the logfile
Tom Lane wrote:
>
> Mark Rae <[EMAIL PROTECTED]> writes:
> > ERROR: copy: line 26501638, insert_fsm_page_entry: failed to insert entry!
>
> Ugh. I think I see the problem: silly oversight in this routine.
> Please apply the attached patch and see if it fixes the f
POSTGRESQL BUG REPORT TEMPLATE
Your name : Mark Jeacocke
Your email address : [EMAIL PROTECTED]
System
Martin Pitt wrote:
> Hi Tom, hi Mark,
>
> Tom, thank you for having a look into this!
>
> Tom Lane [2007-03-29 13:49 -0400]:
>
>> Martin Pitt <[EMAIL PROTECTED]> writes:
>>
>>> https://launchpad.net/bugs/93042 has symbolic gdb backtraces
The following bug has been logged online:
Bug reference: 3847
Logged by: Mark Reid
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Debian Linux
Description:plpython trigger caches table structure - doesn't see
new / changed co
The trigger function does not recognize the "test4" column the second time
it is added - the update throws an error.
On Jan 1, 2008 11:17 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Mark Reid" <[EMAIL PROTECTED]> writes:
> > If a column is added, dropped
Works perfectly on my test case. Thanks!
On Jan 1, 2008 8:07 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Mark Reid" <[EMAIL PROTECTED]> writes:
> > The trigger function does not recognize the "test4" column the second
> time
> > it is adde
We've run our real-life test cases and they've all worked properly using
this patch too. Thanks again.
-Mark.
On Jan 1, 2008 8:07 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Mark Reid" <[EMAIL PROTECTED]> writes:
> > The trigger function does not recog
objects?)
Now, I'm conscious that there could be other show stopper reasons for
*not* doing this that I have not thought of, but figured I'd post in
case the idea was useful. Thoughts?
Cheers
Mark
*** src/backend/commands/tablecmds.c.orig Wed Jan 2 13:58:05 2008
--- src/backend/com
The following bug has been logged online:
Bug reference: 4059
Logged by: Mark Steben
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Linux redhat
Description:Vacuum full not always cleaning empty tables
Details:
I sent an email to
Yes, there are transactions that predate the start time of the vacuum full.
However those transactions do not touch the table being vacuumed, they have
nothing to do with it. Is this the expected behavior?
Mark Steben
Senior Database Administrator
@utoRevenueT
A Dominion Enterprises Company
there was probably a reason why this
had not been tried!).
Best wishes
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
on bug-- the location of that
documentation should be spit out along with the above error message, along with
being accessible through "initdb --help" and perhaps elsewhere.
I look forward to another great release. Thanks!
-mark
http://mark.stosber
On Tue, 1 Oct 2002, Tom Lane wrote:
> Mark Stosberg <[EMAIL PROTECTED]> writes:
> > I think the bug here is that this message advertises that I can change
> > the "max_connections" parameter to address this, but there does not
> > appear to be a way to do
puter as I write
this and
I don't remember the error message. I will send more info on that later.)
I hope this all helps. Let me know if you need any more info.
Mark Iszler
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ly test for problems like this.)
3. If there's some really elegant solution out there, such as a
way to do a "select for update where not locked" to search for
rows no one has a conflicting lock on. (To me this would seem
to be the best of all possible solutio
On Wed, 2003-12-17 at 14:02, Tom Lane wrote:
> Mark Shewmaker <[EMAIL PROTECTED]> writes:
> > In other words: Is this a bug or a user misunderstanding:
>
> You've got the function doing
>
> > LOOP
> > select * into myrow from mytable limit 1
On Wed, 2003-12-17 at 19:57, Tom Lane wrote:
> Mark Shewmaker <[EMAIL PROTECTED]> writes:
> > If a "FOR UPDATE executes before LIMIT" rule stopped the function
> > from ever locking a row, it's still curious why didn't it stop the
> >
ot;
char bound_waiting_state = static_cast < char > ( Processor : :
waiting ) ;
/* exec sql end declare section */
#line 93 "Schedule.pgcc"
The scope operator becomes space padded and compiler barfs.
Work around is to initialise variables outside of declare sect
lt;mailto:[EMAIL PROTECTED]>>) and Michael Meskes (<[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>).
Regards,
Mark Pether.
Michael Meskes wrote:
On Wed, Dec 17, 2003 at 03:14:31PM -0500, Mark Pether wrote:
Ecpg pretty prints my code causing compile errors.
Please note that ecpg
e --with-CXX --with-includes=/opt/csw/include/openssl
Any suggestions ?
Thanks in advance,
-Mark
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
2 NULL
(1 row affected)
1> select 2 as id, max(myfield) from mytable having 2=1
2> go
id
--- --
(0 rows affected)
--
Mark Shewmaker
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3:
rows.
A plain "select 1 from tab" returns zero rows when tab is empty.
--
Mark Shewmaker
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Tom Lane wrote:
Would those of you with access to other DBMSes try this:
create table tab (col integer);
select 1 from tab having 1=0;
select 1 from tab having 1=1;
insert into tab values(1);
insert into tab values(2);
select 1 from tab having 1=0;
select 1 from tab having 1=1;
I claim that a SQL-c
The following bug has been logged online:
Bug reference: 1671
Logged by: Mark Dilger
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.2
Operating system: Mandrake Linux 9.1 (2.4.21-0.13mdkenterprise #1 SMP)
Description:Long interval string representation
poor
schema design is a separate issue.)
Are there any downsides to changing the order of pg_dump output with
respect to constraints? (Versus requiring users to alter their schema
design.)
--
Mark Shewmaker
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
is a snippet of output from a run of vacuumdb --full --analyze
--verbose that should illustrate the problem.
-Mark.
Table Def:
Table "schema_name.properties"
Column | Type| Modifiers
+---+---
name | character varying |
value | character
Matthew T. O'Connor wrote:
Tom Lane wrote:
I think Mark is probably on to something. The activity in the toast
table will show as deletes *in the toast table* ... and that activity
fails to show at all in the pg_stat_activity view, because it shows
only plain relations! So unless autov
mizing the amount of work that needs to be done when a vacuum is
necessary. OTOH, you can't stop regular vacuum from including the
toast table otherwise way more people would start bugging you :)
-Mark.
The following bug has been logged online:
Bug reference: 1874
Logged by: Mark Diener
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.03
Operating system: linux-i686
Description:Non-Execute Privileges enforced on grant
Details:
It seems the EXECUTE privilege
using 'now' and
timestamp() are not recommended practices anyway ?
I have seen that PostgreSQL has already taken the liberty to rewrite
"serial" and other schema constructions when they are dumped or
imported, so I see no problem with rewriting code to equ
On 2005-09-23, Tom Lane <[EMAIL PROTECTED]> wrote:
> Mark Stosberg <[EMAIL PROTECTED]> writes:
>> Why not make the translation on the fly, since using 'now' and
>> timestamp() are not recommended practices anyway ?
>
> Because we can't retroactivel
The following bug has been logged online:
Bug reference: 1970
Logged by: Mark Gibson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: Redhat Enterprise Linux 4
Description:Existing /etc/pam.d/postgresql clobbered by RPM install
Details
The following bug has been logged online:
Bug reference: 2031
Logged by: Mark Gibson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: AIX 5.3 (5300-01)
Description:Patch also required prior to ML3
Details:
Hello,
I've just downloade
Seneca Cunningham wrote:
Mark Gibson wrote:
AIX hasn't had any maintence levels applied yet,
so oslevel -r returns: 5300-01.
_SS_MAXSIZE has been set to 1025 manually, this was
required for 8.0.4.
But with 8.1.0 the patch for dynahash.c had to be
applied before the regression tests woul
g at least
an "=" operator to enable some minimal stats to be available for xml
columns.
regards
Mark
misleading (e.g user error or not
reading the docs), but I don't think we should try (too hard anyway) to
smother any strong criticism.
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 25/05/10 16:43, Mark Kirkwood wrote:
Today I ran into some interesting consequences of the xml data type
being without an "=" operator. One I thought I'd post here because it
has a *possible* planner impact. I'm not sure it is actually a bug as
such, but this seemed th
On 27/05/10 13:37, Mark Kirkwood wrote:
On 25/05/10 16:43, Mark Kirkwood wrote:
Today I ran into some interesting consequences of the xml data type
being without an "=" operator. One I thought I'd post here because it
has a *possible* planner impact. I'm not sure it is act
On 09/06/10 15:22, Robert Haas wrote:
On Thu, Jun 3, 2010 at 7:16 PM, Mark Kirkwood
wrote:
Maybe I gave this guy a bad title - is it a concern that the 'width'
estimate is so far off for xml datatypes (because of no = op)? It seemed to
me that this could result in some bad pl
alculation. However the system allows only the
first, so if you don't (or can't) have one then you lose some possibly
important optimization data.
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresq
On 10/06/10 02:17, Tom Lane wrote:
Mark Kirkwood writes:
It seems that the nub of this issue is that there are conceptually two
types of =, one for datatype specific comparison, and one for optimizer
statistical information calculation. However the system allows only the
first, so if you
On 23/07/10 14:34, vamsi krishna wrote:
Hi
I am running a query on postgres and got the following error:
ERROR: out of memory
DETAIL: Failed on request of size 8
Hmm - looks like your system needs more memory to complete the query
(ahem - would help to see the query, plus EXPLAIN outp
f a downloaded one then
it work work fine (suspect Tom used a checked out tree) Tom?
Cheers
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
iner-clean' removes then, but any lesser level of
clean doesn't. Hmm - shouldn't a VPATH build look at its *own*
doc/src/sgml/*-stamp files to see if it needs to build the docs? Note
that it does *create* them in there after a successful build...
Cheers
Mark
--
Sent via pgsql
The following bug has been logged online:
Bug reference: 5650
Logged by: Mark Llewellyn
Email address: mark_llewel...@adp.com
PostgreSQL version: 9.0 RC1
Operating system: Windows XP
Description:Postgres service showing as stopped when in fact it is
running
Details
here like to fix stuff - but cannot fix your bug unless you
help by supplying what has been asked for.
Best wishes
Mark
On 21/09/10 08:37, Graham Swallow wrote:
Noone else has missing files, in the wrong places,
Its not their problem.
All of the files on all of your machines, are in the right
it fix it for me.
regards
Mark
diff --git a/src/tools/fsync/test_fsync.c b/src/tools/fsync/test_fsync.c
index 3c9c6b6..28c2119 100644
--- a/src/tools/fsync/test_fsync.c
+++ b/src/tools/fsync/test_fsync.c
@@ -63,7 +63,7 @@ main(int argc, char *argv[])
for (i = 0; i < XLOG_SEG_SIZE
ifact of log shipping?
The is 8.3.11 on Debian Lenny x86-64.
Thanks
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 29/10/10 04:32, Alvaro Herrera wrote:
Excerpts from Mark Kirkwood's message of jue oct 28 02:20:56 -0300 2010:
I'm guessing the index error is due to the uninitialized table pages
(the index "content_node_node_type_id_inserted_idx" is on the "node"
table).
t happens if we start it up
and try a VACUUM - however the dbas may have set the box up as a slave
again before we noticed the memory errors (so possibly deleted the old
master).
Cheers
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
The following bug has been logged online:
Bug reference: 5734
Logged by: Mark Stosberg
Email address: m...@summersault.com
PostgreSQL version: 9.0.1
Operating system: FreeBSD
Description:autovacuum_enabled input should be validated,
standardized.
Details:
The
PATH=/usr/local/pgsql/bin:$PATH
$ export LD_LIBRARY_PATH=/usr/local/pgsql/lib
$ initdb -D /data/postgres
$ pg_ctl -D /data/postgres start;
$ psql
I'm guessing that there are older libraries or binaries earlier in your
various env paths, and these are tripping up postgres.
Cheers
Mark
--
Se
vacuum, but any suggestions for getting more diag
info for next time?
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
site, there is no
call for queries that run this long (i.e way longer than the timeout for
the respective page rendering).
Thanks for the clarification (assuming I've understood correctly of
course...).
Cheers
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
1 - 100 of 153 matches
Mail list logo
