On Dec 29, 2011, at 23:25, Jan Bakuwel wrote:
> Hi,
>
> Maybe there is a simple solution for PostgreSQL behaviour that is
> annoying me...
>
> I've got users making updates to a master table and a number of detail
> tables. All changes to the master record and related detail records are
> encap
Hi,
Maybe there is a simple solution for PostgreSQL behaviour that is
annoying me...
I've got users making updates to a master table and a number of detail
tables. All changes to the master record and related detail records are
encapsulated in a transaction so everything can be rolled back if
nec
Hi,
I frequently use pg_dump to dump databases and compare them
with diff. To get rid of most "false positives", I'd like
to patch pg_dump to sort the table so that its dumped order
isn't changed more than necessary by insertions & Co.
So I'm looking for a query that will return a list of a
ta
On 12/29/2011 12:42 PM, Jasen Betts wrote:
On 2011-12-29, Lars Gustafsson wrote:
Hi,
I am trying to recover a lot of deleted rows from a database ( pg
8.2.3 ) , not my database, I promise…..
When using the tool pgfsck I get good results, but timestamp is not implemented.
When trying to expo
On Dec 29, 2011, at 7:08 AM, Lars Gustafsson wrote:
> Hi,
>
> I am trying to recover a lot of deleted rows from a database ( pg 8.2.3 ) ,
> not my database, I promise…..
>
> When using the tool pgfsck I get good results, but timestamp is not
> implemented.
>
> When trying to export as int8
On 2011-12-29, Lars Gustafsson wrote:
> Hi,
>
> I am trying to recover a lot of deleted rows from a database ( pg
> 8.2.3 ) , not my database, I promise…..
>> When using the tool pgfsck I get good results, but timestamp is not
>> implemented.
>
> When trying to export as int8 i get fx. 4
Hi,
I am trying to recover a lot of deleted rows from a database ( pg 8.2.3 ) ,
not my database, I promise…..
When using the tool pgfsck I get good results, but timestamp is not implemented.
When trying to export as int8 i get fx. 4735129360236469258 representing
december 29, 2011, 16