On Wed, Aug 21, 2013 at 11:34 PM, Ivan Radovanovic
wrote:
> On 08/21/13 16:03, Tom Lane napisa:
>
>
> Problem is if you create table in schema other than public (I am not sure if
> \dd should show comments only for objects in public schema, I assumed not?)
>
> db=# create schema test;
> CREATE SCH
On Wed, Aug 21, 2013 at 9:55 PM, carlosinfl . wrote:
> #debug_print_parse = off
> #debug_print_rewritten = off
> #debug_print_plan = off
> #debug_pretty_print = on
> #log_checkpoints = off
> #log_connections = off
> #log_disconnections = off
>
The debug_* will log, well, debug information (e.g.,
On Thu, Aug 22, 2013 at 4:20 AM, 高健 wrote:
> according to a table, How many tuples are heap only tuples , and how many
> are not?
>
I believe there are not "hot tuples", a tuple is updated using HOT
depending on the indexes defined and the type of update itself.
Anyway, you can get an informati
>
> My issue is the logging information is fairly missing / light. I only
> see auth failures and nothing more. I tried to perform my 1st VACUUM
> command on my database and I was hoping to see something in the logs
> showing it PASSED / FAILED or even was manually initiated by a
> superuser role b
Hi:
I have heard that Heap-Only Tuples is introduce from 8.3.
And I am searching information for it.
How can I get a detailed information of HOT?
For example:
according to a table, How many tuples are heap only tuples , and how many
are not?
And also , Is there any options which can influence
Prabhjot,
You could clear the cache at the disk level, not at the db level.
Follow the link: http://linux-mm.org/Drop_Caches
You can look into the cache by using pg_buffercache, if you want to.
Hope it helps
Nik
On Wed, Aug 21, 2013 at 1:31 PM, Prabhjot Sheena <
prabhjot.she...@rivalwatch.com
On Wed, Aug 21, 2013 at 5:09 AM, Fujii Masao wrote:
>> Thu Aug 15 18:33:09 MSK 2013 ERROR archive_wal.sh: Problem occured
>> during WAL archiving: pg_receivexlog: could not send feedback packet:
>> server closed the connection unexpectedly
>>
>> At the same time postgres reported this error in log
or is there a command to flush cache out
Thx
On Wed, Aug 21, 2013 at 1:28 PM, Prabhjot Sheena <
prabhjot.she...@rivalwatch.com> wrote:
> Hi guys
> Is there a way to not cache sql query that just finished
> executing. I have a scenario in which i want to run a sql query but i don't
> w
Hi guys
Is there a way to not cache sql query that just finished
executing. I have a scenario in which i want to run a sql query but i don't
want it to sit in cache. i want it to be cleared from cache as soon as it
displays me the result. Is that possible
Thanks
I'm trying to understand how 9.2.4 logs common tasks and info in
CentOS 6.4 Linux. It appears everything is stored in
/var/lib/pgsql9/data/pg_log/postgresql-%a.log
My issue is the logging information is fairly missing / light. I only
see auth failures and nothing more. I tried to perform my 1st VA
The first thing to do is look at your server logs around the time when
it stopped working.
On Wed, Aug 21, 2013 at 7:08 AM, Joseph Marlin wrote:
> We're having an issue with our warm standby server. About 9:30 last night, it
> stopped applying changes it received in WAL files that are shipped ov
We're having an issue with our warm standby server. About 9:30 last night, it
stopped applying changes it received in WAL files that are shipped over to it
as they are created. It is still reading WAL files as they delivered, as the
startup_log.txt shows, but the changes in the primary database
Just to verify:
- when unique constraint is created using appropriate syntax rows are
added to tables pg_constraint and pg_index (pg_constraint with type 'u'
and referring to index with indisunique set to true)
- when unique index is created row is added only to pg_index table but
not to pg_con
Hi Pavel,
Here are the explains you asked for:
explain analyze select string_agg(id::text,',') from things group by guid;
QUERY PLAN
---
On Wed, Aug 21, 2013 at 10:08 AM, Tom Lane wrote:
> Don Parris writes:
>
>
> initdb will absorb locale/encoding from its environment, unless told
> otherwise through a --locale switch. So the usual expectation would be
> that it'd work like you want. Perhaps the Ubuntu packager set LANG=C i
On 08/21/13 16:34, Ivan Radovanovic napisa:
On 08/21/13 16:03, Tom Lane napisa:
Ivan Radovanovic writes:
I was checking for way to get object comments, and it seems that \dd has
bug when it comes to extracting descriptions for constraints.
That code looks right to me, and it works according t
On 08/21/13 16:03, Tom Lane napisa:
Ivan Radovanovic writes:
I was checking for way to get object comments, and it seems that \dd has
bug when it comes to extracting descriptions for constraints.
That code looks right to me, and it works according to a simple test:
d1=# create table foo (f1
Don Parris writes:
> When I install the Kubuntu (13.04) postgresql (9.1) packages, the default
> template1 encoding turns out to be ASCII, which is not really what I want.
> My OS locale command reveals everything to be en_US.UTF-8, except for
> LC_ALL, which is left open.
initdb will absorb loca
Ivan Radovanovic writes:
> I was checking for way to get object comments, and it seems that \dd has
> bug when it comes to extracting descriptions for constraints.
That code looks right to me, and it works according to a simple test:
d1=# create table foo (f1 int primary key);
CREATE TABLE
d1=#
On Tue, Aug 20, 2013 at 3:17 PM, Sergey Konoplev wrote:
> Hi all,
>
> My WAL archiving script based on pg_receivexlog reported the following
> error several days ago (just ignore everything before
> 'pg_receivexlog', it's a message my script generates).
>
> Thu Aug 15 18:33:09 MSK 2013 ERROR archi
Hi all,
When I install the Kubuntu (13.04) postgresql (9.1) packages, the default
template1 encoding turns out to be ASCII, which is not really what I want.
My OS locale command reveals everything to be en_US.UTF-8, except for
LC_ALL, which is left open.
I am guessing that my best bet is to chang
Hello,
I was checking for way to get object comments, and it seems that \dd has
bug when it comes to extracting descriptions for constraints. Relevant
part of query psql is executing is:
SELECT DISTINCT tt.nspname AS "Schema", tt.name AS "Name", tt.object AS
"Object", d.description AS "Descr
Can i see list of commit related bugs in postgresql. In one of customer,
commit returned successfully but operation is actually committed after an hour
or so successful ( Postgres version -8.1.18).
I am proposing customer to shift to latest version as there is many fixes and
major performance
Thanks Jeff. These queries in particular relate to a set of data that is
rebuilt on a periodic basis. For all intents and purposes, the data is
newly populated and unlikely to reside in cache - hence the need to
perform my tests under similar conditions.
It's probably better than I adjust the ran
Aram Fingal wrote:
> I want to create a user defined data type but have flexible input just like,
> for example, the boolean
> data type where TRUE can be entered as any of (TRUE, true, T, t, YES, yes, Y,
> y, 1...) and it will be
> interpreted as the same thing.
>
> So suppose I have days of th
25 matches
Mail list logo
