On 27.06.2012 10:08, tar...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 6710
Logged by: Tarvi Pillessaar
Email address: tar...@gmail.com
PostgreSQL version: 9.1.4
Operating system: linux
Description:
This happens when epoch is greater t
Hi,
I'll first explain how it is now and then I'll explain how I think it
should behave :-)
I have Postgresql 9.1.4 64bit Linux
- The default tablespace at install is "pg_default" which is (here)
somewhere in /var/lib/...
- The parameter "default_tablespace" in *postgresql.conf* is commented out
r d writes:
> My Database C1 definition:
> CREATE DATABASE "C1" ...
>TABLESPACE = "C1"
> After these two statements, tablespace C1 should be the default tablespace
> for storing all objects in database C1, meaning that when I do not specify
> a tablespace, objects are stored there. Right
On Mon, Jun 25, 2012 at 10:57:56PM +, m.sakre...@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6706
> Logged by: Maciek Sakrejda
> Email address: m.sakre...@gmail.com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Ub
Bruce Momjian writes:
> I can't think of how to fix this. Perhaps we need to query the
> pg_extension table as of the SELECT function all.
I think you're misjudging the core of the issue. The same thing
would happen if somebody dropped and recreated the public schema.
Or anything else that we c
On Fri, Jun 29, 2012 at 11:35:15PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I can't think of how to fix this. Perhaps we need to query the
> > pg_extension table as of the SELECT function all.
>
> I think you're misjudging the core of the issue. The same thing
> would happen if somebo
On Sat, Jun 30, 2012 at 01:00:07AM -0400, Bruce Momjian wrote:
> On Fri, Jun 29, 2012 at 11:35:15PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > I can't think of how to fix this. Perhaps we need to query the
> > > pg_extension table as of the SELECT function all.
> >
> > I think you're
