On Fri, Aug 21, 2009 at 10:36 AM, fabiofurlan wrote:
>
> Hi.
>
> I do not any idea.
>
> When i drop table or alter table, i need restart service postgresql 8.1,
> because is impossible new connect or
> because the changes are not visible.
>
> Gnu Linux Debian 4.0
> PostgreSQL 8.1
>
>
> Thanks a lot
On Wed, Aug 19, 2009 at 5:45 AM, Gaurav K Srivastav wrote:
> HI,
>
> I have a normal user 'abcd' and grant all previliges to this user on the
> database 'pqr'.
> now i am unable to use dblink(text,text).
> while via super user 'postgre' which is the owner of database 'postgre' I
> am able to use
Radoslaw Zielinski writes:
> Greg Stark [2009-08-21 18:55]:
>> Is this, perchance, new hardware? Did you test the memory in it?
> It's a "virtual private server"; the hosting provider is swearing
> everything's fine. I can't vouch for it myself, obviously.
Hmmm ... have you had any crashes? I
2009/8/21 Radoslaw Zielinski :
> Greg Stark [2009-08-21 18:38]:
> [...]
>> the toast table. Not unless you can dump the whole index and find
>> pointers in there or can find the details in the wal log.
>
> You mean the primary key index? How do I dump it?
Actually I mean the key for the toast ta
Greg Stark [2009-08-21 18:38]:
[...]
> the toast table. Not unless you can dump the whole index and find
> pointers in there or can find the details in the wal log.
You mean the primary key index? How do I dump it?
--
Radosław Zieliński
pgpdIiosOzpYQ.pgp
Description: PGP signature
Greg Stark [2009-08-21 18:55]:
[...]
> Is this, perchance, new hardware? Did you test the memory in it?
It's a "virtual private server"; the hosting provider is swearing
everything's fine. I can't vouch for it myself, obviously.
> Do you have other records that have "disappeared"?
I haven't fo
2009/8/21 Radoslaw Zielinski :
> Greg Stark [2009-08-21 18:03]:
>> On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski
>> wrote:
>>> This particular row currently has last_modified="2009-08-11", but table_log
>>> says it has been updated on "2009-08-12" -- so, data loss.
>
>> These are all very l
On Fri, Aug 21, 2009 at 9:36 AM, fabiofurlan wrote:
>
> Hi.
>
> I do not any idea.
>
> When i drop table or alter table, i need restart service postgresql 8.1,
> because is impossible new connect or
> because the changes are not visible.
>
no, you don't have to. you have a specific problem of this
"Sebastien Lardiere" writes:
> Description:pg_freespacemap make a SegFault
There's a post-8.3.7 fix that might cure this:
http://archives.postgresql.org/pgsql-committers/2009-04/msg00108.php
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
Hello
2009/8/21 <94487...@qq.com>:
>
> The following bug has been logged online:
>
> Bug reference: 5001
> Logged by:
> Email address: 94487...@qq.com
> PostgreSQL version: 8.3.3
> Operating system: linux
> Description: can not prepare for where $1 is null
> Details:
>
> why ca
Greg Stark [2009-08-21 18:12]:
[...]
> Or alternatively do you have all the wal logs and could you run
> xlogdump on them looking for transaction id 6179?
Nope, I don't have the wal logs.
--
Radosław Zieliński
pgpO5wPiNs71J.pgp
Description: PGP signature
Greg Stark [2009-08-21 18:03]:
> On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski
> wrote:
>> This particular row currently has last_modified="2009-08-11", but table_log
>> says it has been updated on "2009-08-12" -- so, data loss.
> These are all very low transaction ids. you say it was a we
On Fri, Aug 21, 2009 at 5:15 PM, Alvaro
Herrera wrote:
> I wonder if this could be explained by xid=6179 not marked as committed
> in clog. I'd try flipping that bit and see what happens ...
Well nothing's going to help much now. Firstly, once the hint bit gets
set nothing second-guesses that and
Alvaro Herrera writes:
> I wonder if this could be explained by xid=6179 not marked as committed
> in clog. I'd try flipping that bit and see what happens ...
Once the row's been marked XMAX_INVALID, changing clog won't change that
marking ...
regards, tom lane
--
Sent
The following bug has been logged online:
Bug reference: 5004
Logged by: Sebastien Lardiere
Email address: slardi...@hi-media.com
PostgreSQL version: 8.3.7
Operating system: Debian Etch
Description:pg_freespacemap make a SegFault
Details:
I've got a crash with a clu
Hi.
I do not any idea.
When i drop table or alter table, i need restart service postgresql 8.1,
because is impossible new connect or
because the changes are not visible.
Gnu Linux Debian 4.0
PostgreSQL 8.1
Thanks a lot.
--
View this message in context:
http://www.nabble.com/When-Drop-Ta
The following bug has been logged online:
Bug reference: 5003
Logged by: Pramod
Email address: pramodchoudhar...@yahoo.com
PostgreSQL version: 8.4.0-1
Operating system: Windows XP
Description:setup error
Details:
setup error showing message:
"An error occured while
The following bug has been logged online:
Bug reference: 5001
Logged by:
Email address: 94487...@qq.com
PostgreSQL version: 8.3.3
Operating system: linux
Description:can not prepare for where $1 is null
Details:
why can not prepare like this? thanks!
prepare
Greg Stark wrote:
> It looks like the row *was* updated by transaction 6179 and the new
> version was stored in line pointer 12. However it's marked
> XMAX_INVALID which means at least somebody at some point thought 6179
> had aborted and marked that hint bit.
Hmm, but LP 12 shouldn't have len=0
Radoslaw Zielinski wrote:
> Hello,
>
> 8.4.0 installation on i686 modern Linux, a simple production app with ~4
> users entering data; normalised, no weird stuff happening there. Recently:
>
> ERROR: missing chunk number 0 for toast value 120741 in pg_toast_29644
> bug=# select id, last_modi
On Fri, Aug 21, 2009 at 5:03 PM, Greg Stark wrote:
> On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski
> wrote:
>
> Here's a dump of that page btw.
... [crap word-wrapped by gmail]
Sorry, clearly gmail sucks for posting things that you actually care
about how they're formatted. I've attached th
On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski wrote:
> This particular row currently has last_modified="2009-08-11", but table_log
> says it has been updated on "2009-08-12" -- so, data loss.
These are all very low transaction ids. you say it was a week of
production before this happened?
Hello,
8.4.0 installation on i686 modern Linux, a simple production app with ~4
users entering data; normalised, no weird stuff happening there. Recently:
ERROR: missing chunk number 0 for toast value 120741 in pg_toast_29644
This table has table_log and a "before update" trigger setting
"NE
Hi Annita-san.
Thank you for many report.
However, It is a very strange situation... that visible problem resembles the
phenomenon in which libpq.dll is only not found. Therefore, there is information
I want you to check.
1. Is libpq.dll in the place of installed psqlodbc35w.dll?
ex.)
C:\Progra
24 matches
Mail list logo
