AFAICT, this is something that should have been designed into the initial
release of PostgreSQL, but rather than go down that road, I have thought
about this and will attempt to explain the "complexity" of implementing it,
which to date has only been described as too hard or, we don't have enough
d
On 12/24/19 8:58 PM, Rob Sargent wrote:
On Dec 24, 2019, at 11:48 AM, Ron wrote:
On 12/24/19 1:14 PM, Rob Sargent wrote:
If there's not enough time and motivation for the developers to implement
CREATED_ON and LAST_ALTERED in pg_class, then you should have said that in the
first place.
> On Dec 24, 2019, at 11:48 AM, Ron wrote:
>
> On 12/24/19 1:14 PM, Rob Sargent wrote:
>>
>>> If there's not enough time and motivation for the developers to implement
>>> CREATED_ON and LAST_ALTERED in pg_class, then you should have said that in
>>> the first place. We're adults; we unde
On 12/24/19 1:14 PM, Rob Sargent wrote:
If there's not enough time and motivation for the developers to implement
CREATED_ON and LAST_ALTERED in pg_class, then you should have said that in the
first place. We're adults; we understand that OSS projects have limited
resources, and won't go off
> If there's not enough time and motivation for the developers to implement
> CREATED_ON and LAST_ALTERED in pg_class, then you should have said that in
> the first place. We're adults; we understand that OSS projects have limited
> resources, and won't go off and pout in the corner.
>
> Bu
On 12/24/19 12:14 PM, Adrian Klaver wrote:
On 12/24/19 8:44 AM, Ron wrote:
On 12/24/19 10:39 AM, Adrian Klaver wrote:
On 12/23/19 6:14 PM, Ron wrote:
On 12/23/19 7:01 PM, Bruce Momjian wrote:
Is this something that has been considered for implementation?
I wrote a blog about this:
https:/
On 12/24/19 8:44 AM, Ron wrote:
On 12/24/19 10:39 AM, Adrian Klaver wrote:
On 12/23/19 6:14 PM, Ron wrote:
On 12/23/19 7:01 PM, Bruce Momjian wrote:
Is this something that has been considered for implementation?
I wrote a blog about this:
https://momjian.us/main/blogs/pgblog/2017.html#Nove
On 12/24/19 10:39 AM, Adrian Klaver wrote:
On 12/23/19 6:14 PM, Ron wrote:
On 12/23/19 7:01 PM, Bruce Momjian wrote:
On Thu, Dec 5, 2019 at 05:10:20PM +, Chloe Dives wrote:
Having moved to PostgreSQL from Oracle a few years ago I have been
generally
very impressed by Postgres, but there a
On 12/23/19 6:14 PM, Ron wrote:
On 12/23/19 7:01 PM, Bruce Momjian wrote:
On Thu, Dec 5, 2019 at 05:10:20PM +, Chloe Dives wrote:
Having moved to PostgreSQL from Oracle a few years ago I have been generally
very impressed by Postgres, but there are a few things that I still miss. One
of th
Em seg., 23 de dez. de 2019 às 23:14, Ron
escreveu:
>
> You all are grossly over-complicating this.
>
Maybe we are really very conservative, but everyone needs to
understand that every single piece of code added to core is our
responsibility to maintain and make sure don't break the whole thing.
Ron schrieb am 24.12.2019 um 03:14:
Having moved to PostgreSQL from Oracle a few years ago I have been generally
very impressed by Postgres, but there are a few things that I still miss. One
of those is being able to see the created and last modified dates for database
objects.
Is this something
>You all are *grossly* over-complicating this.
Agree +1
On Mon, Dec 23, 2019 at 9:14 PM Ron wrote:
> On 12/23/19 7:01 PM, Bruce Momjian wrote:
>
> On Thu, Dec 5, 2019 at 05:10:20PM +, Chloe Dives wrote:
>
> Having moved to PostgreSQL from Oracle a few years ago I have been generally
> very
On 12/23/19 7:01 PM, Bruce Momjian wrote:
On Thu, Dec 5, 2019 at 05:10:20PM +, Chloe Dives wrote:
Having moved to PostgreSQL from Oracle a few years ago I have been generally
very impressed by Postgres, but there are a few things that I still miss. One
of those is being able to see the crea
On Thu, Dec 5, 2019 at 05:10:20PM +, Chloe Dives wrote:
> Having moved to PostgreSQL from Oracle a few years ago I have been generally
> very impressed by Postgres, but there are a few things that I still miss. One
> of those is being able to see the created and last modified dates for databas
On 12/5/19 7:40 PM, Michael Paquier wrote:
On Thu, Dec 05, 2019 at 07:12:22PM -0600, Ron wrote:
On 12/5/19 1:01 PM, Tom Lane wrote:
It's been considered, and rejected, many times. Aside from the overhead
involved, there are too many different ideas of what such dates ought to
mean (e.g., what
On Thu, Dec 05, 2019 at 07:12:22PM -0600, Ron wrote:
> On 12/5/19 1:01 PM, Tom Lane wrote:
>> It's been considered, and rejected, many times. Aside from the overhead
>> involved, there are too many different ideas of what such dates ought to
>> mean (e.g., what should happen during dump/restore? d
On 12/5/19 1:01 PM, Tom Lane wrote:
Chloe Dives writes:
Having moved to PostgreSQL from Oracle a few years ago I have been generally
very impressed by Postgres, but there are a few things that I still miss. One
of those is being able to see the created and last modified dates for database
On 12/5/19 9:10 AM, Chloe Dives wrote:
Having moved to PostgreSQL from Oracle a few years ago I have been
generally very impressed by Postgres, but there are a few things that I
still miss. One of those is being able to see the created and last
modified dates for database objects.
Is this som
Hi Tom
can't we get access to this information in a backwards way by using
pg_xact_commit_timestamp() then query the system catalog tables xmin entry
for the relevant object???
this requires turning on pg_xact_commit_timestamp
https://www.postgresql.org/docs/current/runtime-config-replication.ht
Chloe Dives writes:
> Having moved to PostgreSQL from Oracle a few years ago I have been generally
> very impressed by Postgres, but there are a few things that I still miss. One
> of those is being able to see the created and last modified dates for
> database objects.
> Is this something that
Having moved to PostgreSQL from Oracle a few years ago I have been generally
very impressed by Postgres, but there are a few things that I still miss. One
of those is being able to see the created and last modified dates for database
objects.
Is this something that has been considered for imple
21 matches
Mail list logo
