On 11/07/2012 05:09 AM, Igor Neyman wrote:
>
> Hi,
>
>
>
> Where in pg_catalog I can find, if the table was created as "unlogged"
> (or not)?
>
> As in: create unlogged table t1(c1 int);
>
> I can't seem to find this info in pg_catalog tables/views.
>
>
>
> Tried psql with --E to describe (\d)
On Nov 6, 2012, at 4:56 PM, Deron wrote:
> Yes, I can't really find a good use case for it. I am meeting with some of
> them in the next few days to find out exactly what they are using it for. If
> there is a legitimate use case for this, I will forward that information.
>
> Thanks for the
Yes, I can't really find a good use case for it. I am meeting with some
of them in the next few days to find out exactly what they are using it
for. If there is a legitimate use case for this, I will forward that
information.
Thanks for the suggestions. I will pass this information along as w
On 6 November 2012 23:25, Tom Lane wrote:
> Deron writes:
>> We are looking at integrating a 3rd party application. They currently use
>> MySQL for their database solution. We are asking them to see about porting
>> to PostgreSQL. One of the issues they are running into is that they use
>> My
On Tue, Nov 6, 2012 at 3:07 PM, Deron wrote:
> We are looking at integrating a 3rd party application. They currently use
> MySQL for their database solution. We are asking them to see about porting
> to PostgreSQL. One of the issues they are running into is that they use
> MySQL "BLACKHOLE" st
Deron writes:
> We are looking at integrating a 3rd party application. They currently use
> MySQL for their database solution. We are asking them to see about porting
> to PostgreSQL. One of the issues they are running into is that they use
> MySQL "BLACKHOLE" storage engine.
Really? I've al
Hello,
We are looking at integrating a 3rd party application. They currently use
MySQL for their database solution. We are asking them to see about porting
to PostgreSQL. One of the issues they are running into is that they use
MySQL "BLACKHOLE" storage engine.
I don't honestly know what this
Edwin Grubbs writes:
> Redhat cluster comes with a default configuration file for
> postgres-8.4 that by default just sends a SIGQUIT to stop postgres.
Ouch. That's news to me.
> I can't find any more information on why not to use SIGQUIT besides
> the documentation indicating "This is recomme
From: Igor Neyman
Sent: Tuesday, November 06, 2012 4:09 PM
To: pgsql-admin@postgresql.org
Subject: unlooged tables
Hi,
Where in pg_catalog I can find, if the table was created as "unlogged" (or not)?
As in: create unlogged table t1(c1 int);
I can't seem to find this info in pg_catalog tables/vie
Hi,
Where in pg_catalog I can find, if the table was created as "unlogged" (or not)?
As in: create unlogged table t1(c1 int);
I can't seem to find this info in pg_catalog tables/views.
Tried psql with -E to describe (\d) unlogged table, but it was not helpful.
Regards,
Igor Neyman
Redhat cluster comes with a default configuration file for
postgres-8.4 that by default just sends a SIGQUIT to stop postgres.
I'm trying to convince Redhat support to use SIGINT instead of
SIGQUIT, so that postgres doesn't have to recover by replaying the WAL
file, but they are questioning whether
11 matches
Mail list logo
