Hi
Is there any chances for any performance issues with pg_restore when changing
the servers, like openvz, xen, etc.? Will the server difference make the time
of restore longer in this case?
ThanksArun
On Thu, Feb 27, 2014 at 11:17 PM, Adrian Klaver
wrote:
> That works because you said NULL is a valid value for the column. If you
> had specified NOT NULL then you would get an error about violating the NOT
> NULL constraint. Since you have said NULL is a valid value and you actually
> specified i
I see that I can use PQgetResult to get results from an async query, and this
allows for multiple results, presumably when the query is like "SELECT 123,
456; SELECT 'ABC', 'DEF';". Is there a way for a C function, using SPI, to send
result sets without waiting for completion and returning a pot
On Thu, Feb 27, 2014 at 7:39 AM, Vinay Gupta wrote:
> 1078769 s/d/r:1663/1228184/5263108,insert_leaf:
> 1155642 s/d/r:1663/1228184/5263105,insert:
> 1181241 s/d/r:1663/1228184/5263107,insert_leaf:
>
> Is dere any better way where i can analyse who is contributing most in my
> pgxlog file generat
On 02/27/2014 08:51 AM, Dev Kumkar wrote:
On Thu, Feb 27, 2014 at 9:32 PM, Adrian Klaver
mailto:adrian.kla...@aklaver.com>> wrote:
Realized my previous answer:
col_2 = coalesce(my_test.col_2, NEW.col_2)
works for the particular situation you described, but not for the
general
On Thu, Feb 27, 2014 at 9:32 PM, Adrian Klaver wrote:
>
> Realized my previous answer:
>
> col_2 = coalesce(my_test.col_2, NEW.col_2)
>
> works for the particular situation you described, but not for the general
> case. It would not allow an update of a field where a NON NULL value exists
> and yo
On 02/27/2014 03:45 AM, Dev Kumkar wrote:
Am facing issues with using UPSERT rule having default value columns.
Here is the code:
create table my_test (id int, col_1 timestamp null, col_2 varchar(12)
null default 'Initial');
CREATE OR REPLACE RULE RULE_my_test AS ON INSERT TO my_test WHERE
EX
Thanks David for your quick response. My original objective was to get the
value of a particular node in xml which is stored as text datatype in the
table.
For example :
--16
I want to extract the value of amperage as '16'. Like that I may have many
nodes in xml want to get the report to show
Hi,
My current database version is "PostgreSQL 9.1.11 on
x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat
4.4.7-3), 64-bit".
I am trying to use function xpath in my query and got following error.
"ERROR: function xpath(unknown, text) does not exist at character 8
HINT:
Hi All;
We're talking with a HW / Data Center company about scaling up our DB
servers... Below are some questions they asked relaed to moving to SSD's
or maybe a Fusion IO drive.
Anyone have any thoughts, specifically on the queue depth question?
Thanks in advance...
/So our question I thi
On Wed, Feb 26, 2014 at 5:40 PM, Steve Crawford
wrote:
> On 02/26/2014 08:56 AM, Alvaro Herrera wrote:
>>
>> ...
>>
>> No matter how heavily updated, regular activity should not cause
>> autovacuum kills. Only heavier operations would do that (say ALTER
>> TABLE, etc).
>
>
> "Considered harmful"
Hi,
Is dere any better way we can understand the contents of pg_xlog files. I
am using xlogdump for analysing my xlog contents. Sometimes in my database
server in some particular hours, the pgxlog files generation exceeded than
the expected counts almost 3X than the normal count.
*--- Size of 1
On 02/27/2014 03:45 AM, Dev Kumkar wrote:
Am facing issues with using UPSERT rule having default value columns.
Here is the code:
create table my_test (id int, col_1 timestamp null, col_2 varchar(12)
null default 'Initial');
CREATE OR REPLACE RULE RULE_my_test AS ON INSERT TO my_test WHERE
EX
James Harper wrote:
> Just a minor bug in the documentation -
> http://www.postgresql.org/docs/9.3/static/bgworker.html says that bgw_main
> takes an argument of void*, but when declared as such gcc -Wall gives a
> warning of:
>
> init.c:59:19: warning: assignment from incompatible pointer type
Am facing issues with using UPSERT rule having default value columns.
Here is the code:
create table my_test (id int, col_1 timestamp null, col_2 varchar(12) null
default 'Initial');
CREATE OR REPLACE RULE RULE_my_test AS ON INSERT TO my_test WHERE EXISTS
(SELECT 1 from my_test WHERE id = NEW.i
Just a minor bug in the documentation -
http://www.postgresql.org/docs/9.3/static/bgworker.html says that bgw_main
takes an argument of void*, but when declared as such gcc -Wall gives a warning
of:
init.c:59:19: warning: assignment from incompatible pointer type [enabled by
default]
worker
16 matches
Mail list logo
