main problem is how the default
database can be created and restore of the data can be done automatically
using some script or so. Any suggestion or idea are welcome.
Thanks in advance.
Regards,
Amit
main problem is how the default
database can be created and restore of the data can be done automatically
using some script or so. Any suggestion or idea are welcome.
Thanks in advance.
Regards,
Amit
r and rest of slave
nodes, how can I take backup of this distributed database to one of my
other server or backup location.
Please suggest me what would be the best approch for this.
--
Thanks & Regards,
Amit Bondwal
Thanks you very much Craig for clearing these facts and sorry for mail sent
only to you by mistake.
--
Thanks & Regards,
Amit Bondwal
On Fri, Jul 17, 2015 at 6:19 PM, Craig Ringer wrote:
> On 17 July 2015 at 19:37, Amit Bondwal wrote:
> > Thank you very much all of you for q
on client machine?
I am using linux as a clinet machine and want to connect through command
line, without client certificate in encrypted format or on SSL. What should
I do?
--
Thanks & Regards,
Amit Bondwal
Contact me at +91-999-0235-948
Thanks you very much Adrian for clearing my confusion.
On Mon, Jul 27, 2015 at 7:24 PM, Adrian Klaver
wrote:
> On 07/27/2015 12:48 AM, Amit Bondwal wrote:
>
>> Hi Everyone.
>>
>> I am able to setup postgresql with TLS v1.2 with client certificate. I
>> used b
debian squeeze or it was on debian
wheezy on different hardwares or VPS servers.
Is there any different way to do replication to avoid this issue? or how
can I resolve this issue.
--
Regards
Amit Bondwal
8-21 15:40:20 IST [21561-1] FATAL: incorrect checksum in control file
It gives the error "database system identifier differs between the primary
and standby".
On Fri, Aug 21, 2015 at 3:26 PM, Amit Bondwal
wrote:
> Hi everyone,
>
> I am trying to setup postgresql 9.3 hot
Michael, Thanks for your reply, I found the issue, the person who setup OS
mix up some 64 and 32 bit package. I am starting it again.
Thanks again.
On Fri, Aug 21, 2015 at 5:12 PM, Michael Paquier
wrote:
>
>
> On Fri, Aug 21, 2015 at 7:56 PM, Amit Bondwal
> wrote:
>
>> 20
marking the costs could have avoided that (as explained above). Note that
I am not suggesting that ordering quals in query by their perceived cost
is the solution. Keep optimizer informed by setting costs appropriately
and it will do the right thing more often than not. :)
Thanks,
Amit
--
Sent
san will be better able to explain and correct if the above
rough sketch is not exactly accurate)
Thanks,
Amit
[1]
https://www.postgresql.org/docs/9.6/static/runtime-config-query.html#RUNTIME-CONFIG-QUERY-CONSTANTS
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
ren of parent. Having failed to do that, it encounters the
error in question when further along it tries to find parent's
attributes in somechild which are no longer there (remember, other
session just disinherited parent). That perhaps needs some fixing. I
may be missing though.
Thanks,
Amit
recreate it but same error. I
also tried to connect to 2nd node as external dsn but same error.
I am able to access all three nodes to each other using psql.
--
Regards
Amit Bondwal
On Tue, Dec 22, 2015 at 10:05 AM, Craig Ringer
wrote:
> select * from bdr.bdr_connections;
>
Hi Craig, Thanks for your reply, These commands shows nothing on 3rd node.
*on node3:-*hakuna=# select * from bdr.bdr_nodes;
node_sysid | node_timeline | node_dboid | node_status | node_name |
node_
Hi Craig,
I remove all the bdr packages and reinstall it and setup again the BDR
cluster, still facing the same issue on 3rd node.
On Tue, Dec 22, 2015 at 10:58 AM, Amit Bondwal
wrote:
>
> On Tue, Dec 22, 2015 at 10:05 AM, Craig Ringer
> wrote:
>
>> select * from b
015 at 17:00, Amit Bondwal wrote:
>
>
>> I remove all the bdr packages and reinstall it and setup again the BDR
>> cluster, still facing the same issue on 3rd node.
>>
>
> At this point I'd really need to see the steps taken, in detail, to get to
> that point fr
stdb
$ pg_dump srcdb | psql destdb
$ psql destdb
psql (9.6devel)
Type "help" for help.
destdb=# \d
List of relations
Schema | Name | Type | Owner
+--+---+---
public | p| table | amit
(1 row)
destdb=# CREATE TABLE c (LIKE p);
CREATE TABLE
destd
appreciate your help take it on urgent basis plz.
Amit Jain.
iBoss Tech Solution Ltd.
sec-63 Noida.
Hello -
I'm trying to findout a better solution to this approach.
Currently if I have to return columns from multiple tables, I have to
define my own TYPE and then return SETOF that type in the function.
I've provided an example below.
Now, if I have to add a column to the select qu
Hello -
I'm trying to findout a better solution to this approach.
Currently if I have to return columns from multiple tables, I have to
define my own TYPE and then return SETOF that type in the function.
I've provided an example below.
Now, if I have to add a column to the select qu
.16.08 rows=10 width=0)
Index Cond: (((a)::text || (b)::text) ~~ '%c4c%'::text)
Planning time: 0.361 ms
(5 rows)
--
Amit
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Aug 1, 2014 at 2:50 PM, Amit Langote wrote:
>
> Not sure exactly if it applies here;
Re-reading the OP again, perhaps it doesn't. Sorry about the noise
--
Amit
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscri
't come through,
> presumably because it was considered to be spam.
>
> Where would be a more appropriate place to make such an announcement?
>
Take a look at this page:
http://www.postgresql.org/list/
pgsql-announce is the list you are looking for.
--
Amit
--
Sent via pgsql-gen
ese
parameters are USERSET parameters,
so no need to change config file and reload or restart.
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ct, then the rows will be
locked during whole transaction
irrespective of the fact that they will not be updated.
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Sunday, January 06, 2013 11:10 AM Amit kapila wrote:
On Sunday, January 06, 2013 7:48 AM Chris Travers wrote:
>> Is there a reason why we don't do locking this way? (i.e. where on UPDATE
>> foo, all rows selected from foo during the
>> update are locked unless the
You can try once with below query:
Select * from (SELECT a.id,b.value FROM table_a a, table_b b WHERE ... AND ...
) X where X.value=...;
If this doesn't work can you send the Explain .. output for both queries(the
query you are using and the query I have suggested)
With Regards,
Amit Kapila.
om columns in the
database as the
> parameters of a set-returning function from which I want to select *.
Can you try with RETURN NEXT syntax. For example, refer below link:
http://www.postgresql.org/docs/9.2/static/plpgsql-control-structures.html#PL
PGSQL-STATEMENTS-RETURNING
With Regards,
;dim_id" IS NULL
> Line: 1
>
> [Executed: 2/4/13 11:07:08 PM PST ] [Execution: 0/ms]
>
>
> exception.
>
> Is there anything i am missing.
Why the query is different in Exception?
Can you try with
SELECT
tbl.id,
tbl.day,
tbl.week,
t
ght, then you can try with using DISTINCT operator:
http://www.postgresql.org/docs/9.2/static/sql-select.html#SQL-DISTINCT
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
on, will this problem remains.
Is there any chance that the block gets corrupted due to hardware problem?
2. missing clog files - how did you find missing clog files, is any
operation got failed or just an observation?
Do you see any problems in system due to it?
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
> -Original Message-
> From: Merlin Moncure [mailto:mmonc...@gmail.com]
> Sent: Friday, February 15, 2013 7:56 PM
> To: Amit Kapila
> Cc: Ben Chobot; PostgreSQL General
> Subject: Re: [GENERAL] bug, bad memory, or bad disk?
>
> On Fri, Feb 15, 2013 at 8:08
server should start with
Pg_ctl.exe start -D data_dir
Where data_dir is the path where you have created your database.
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
llowed on that relation. Most of admin care about
this point, because
they don't want to stop operations for background garbage collect.
VACUUM FULL is only done in rare cases when the relation size has grown too
bigger than it's actual
Contents.
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I was just going through the xlog.c and I came across following which
confused me:
Given,
src/include/access/xlogdefs.h
#define XLogSegsPerFile (((uint32) 0x) / XLogSegSize)
#define XLogFileSize(XLogSegsPerFile * XLogSegSize)
Also,
typedef struct XLogRecPtr
{
uint32
> position
> --
> 1
> (1 row)
>
> Kindly let me know, if anything i miss here.
>
> Regards,
> Dinesh
> manojadinesh.blogspot.com
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
something similar, it returns first
index (which is 1) of the main string (haystack!). Although this does
not answer if it's a bug or not, I tend to think it is deliberate.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your sub
r, if you specify -W option, psql won't connect before it
accepts password. You can try this (and see that no authentication
failure is logged)
I think log entries just mean the authentication has failed with
PAM-specific error message.
--
Amit Langote
--
Sent via pgsql-general ma
g is a bug in PAM authentication code in the
backend that needs to resolved. This has been reported on
pgsql-hackers.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
you understand distinct phases of connection and subsequent
operation over the established connection.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Sat, May 18, 2013 at 1:25 AM, Jeff Amiel wrote:
> On most nested loops that I do explain/explain analyze on, the row estimation
> for the nested-loop itself is a product of the inner nodes of the nested loop.
> However in this case, I am stumped!
>
> explain
> select era.child_entity from en
On Sat, May 18, 2013 at 1:47 AM, Jeff Amiel wrote:
>
>
>
>
> - Original Message -----
> From: Amit Langote
> To: Jeff Amiel
> Cc: "pgsql-general@postgresql.org"
> Sent: Friday, May 17, 2013 11:37 AM
> Subject: Re: [GENERAL] Why does row estimati
ted to the fact that the nested-loop
> row estimation does not appear to be derived from the nodes below it - it is
> off by orders of magnitude. I've never seen this before.
> That aside, yes - I did analyze and tweak stats target during experimentation
> - no change.
Did you
c/row-estimation-examples.html
It also refers where in source code these table size estimations are done.
Hope this helps.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I also found one other discussion which has similar issues addressed:
http://postgresql.1045698.n5.nabble.com/Bogus-nestloop-rows-estimate-in-8-4-7-td5710254.html
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
ould like to know if you still get the
same row estimates (after explain) and also if possible, the value
that is computed from that formula. Do they resemble each other?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
65.81
> rows=580 width=8)
> Filter: ((algorithm)::text = 'SMAT'::text)
> Does anyone have suggestions about how to speed it up?
Could you please once trying Analyzing both tables and then run the query to
check which plan it uses:
Analyze SARS_ACTS;
An
n future Hash Join might be the best and cheapest way.
Can you try reproducing it with small data or else can you attach your schema
and data for the tables/indexes used in query?
With Regards,
Amit Kapila.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
27;s okay using 9.2 pg_receievexlog with a 9.1 server.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ovacuum launcher, which periodically forks autovacuum worker
processes to perform vacuum activity. You might want to read more
about them here:
http://www.postgresql.org/docs/9.2/static/routine-vacuuming.html#AUTOVACUUM
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql
r do you have a backup you could
restore to using PITR?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e would have to wait for others to reply on this thread to
point out any others means to recover your data, if any.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
nd of default max or
something like that for such abnormal cases?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
sets the start cost to the high value (100).
>
Oh, okay, thanks!
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
> When one uses “enable_” settings to adjust planner behavior, PostgreSQL
> just sets really high costs for the operations affected (like the one you
> see).
>
> As SeqScan is the only possible way to execute your query, it is still
> choosen.
>
I get it. Thanks!
--
Amit L
g is to have
> frequent, tested, backups.
>
How does one validate a backup? Is there any generally practiced way
of doing that? Or what do you mean when you say "tested" backups?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make change
|3548 | 3547
abc_2_idx|3209 | 3209
...
...
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, Jun 4, 2013 at 12:17 PM, Jeff Janes wrote:
> On Monday, June 3, 2013, Amit Langote wrote:
>>
>> Hello,
>>
>> In what cases can a relation use more buffers (in shared memory) than
>> its pg_class.relpages?
>
>
> I think relpages only counts page
On Tue, Jun 4, 2013 at 10:04 PM, Andres Freund wrote:
> On 2013-06-04 11:29:44 +0900, Amit Langote wrote:
>> In what cases can a relation use more buffers (in shared memory) than
>> its pg_class.relpages?
>
> relpages is primarily updated by (auto-)vacuum, (auto-)analyze, so
o
> write a function that just ignores the third argument.
>
Just wondering:
If this particular function is to be used repeatedly in a single
query, would the cost of having a wrapper function around the original
function be too large? For example, if this function appears in a
WHERE clause
Hi,
On Thu, Jun 20, 2013 at 10:27 AM, Chris Angelico wrote:
> On Thu, Jun 20, 2013 at 11:10 AM, Amit Langote
> wrote:
>> If this particular function is to be used repeatedly in a single
>> query, would the cost of having a wrapper function around the original
>> fu
On Thu, Jun 20, 2013 at 10:54 AM, Chris Angelico wrote:
> On Thu, Jun 20, 2013 at 11:35 AM, Amit Langote
> wrote:
>> On Thu, Jun 20, 2013 at 10:27 AM, Chris Angelico wrote:
>>> If your wrapper function is written in SQL and is trivial (eg ignore
>>> the third pa
On Thu, Jun 20, 2013 at 11:10 AM, Chris Angelico wrote:
> On Thu, Jun 20, 2013 at 12:09 PM, Amit Langote
> wrote:
>> Umm, my bad! I almost forgot I could write pure SQL function bodies.
>> Although, why does following happen? (sorry, a 8.4.2 installation) :
>>
>>
d/1718942738eb65c8407fcd864883f...@fuzzy.cz
When I checked on my 9.4dev installation, I found $PGDATA/pg_stat and
there were per database .stat files.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ts across
server restarts, which, might even be applicable to a PITR, as far as
I can understand. This would need some testing, though, to be sure
that it is the case.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
On Thu, Jun 20, 2013 at 8:32 PM, Amit Langote wrote:
> On Thu, Jun 20, 2013 at 6:05 PM, Sameer Thakur wrote:
>>>Documentation mentions following:
>> Thanks, but how does this relate to statistics recovery wrt PITR?
>
> Upon clean server shutdown, you have the statisti
s, of
pg_stat/*.stat), though I am not sure if that would be correct. I
doubt if WAL replay (as in a consistent recovery mechanism :-) )
accounts for the stats. I guess stats are not WAL logged (like changes
to table data) since they are managed using temporary files in
pg_stat_temp and hence may not be recoverable using WAL replay to a
particular state using PITR. but I may be wrong.
Thoughts?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
sue it? Is that after OS restarts?) Did you, by any chance, use
"restart" whereas you should have used "start" assuming you are using
pg_ctl for the same?
Issuing "restart" requires that you should already have server running
(and that means postmaster.pid should be the
-
>
> select to_oid('testdata');
>
> Can anyone tell me that how I can implement above function for conversion?
>
Sachin, check if this link is related:
http://stackoverflow.com/a/10139455/683402
+
Here (from official PG docs):
http://www.postgresql.org/docs/9.2/sta
Surprisingly it
> works with no complaints about wrong pgstat.stats
>
Do you have only one archive set up? What do you mean when you mention
"backup1" archive?
What kind of complaints did you see when you did in past? I am not
aware of such errors; am I missing some?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tats reporting tool (like
pg_statsinfo) would be the only way to preserve such historic
(snapshots-like) information about those statistics. Server itself
doesn't have any mechanism to preserve any historical information like
those stats, am I right in saying that?
--
Amit Langote
--
l_keep_segments ?
>
> I know that I can increase wal_keep_segments to "solve" it, but
> shouldn't it be *impossible* to happen with synchronous replication?
> After all - all commits should wait for slave to be 100% up to date!
>
Is it possible that xlog recycling might have
? That would be helpful.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
anyway. Does that make
sense?
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, Jul 23, 2013 at 1:11 PM, Amit Langote wrote:
> Hello,
>
> While understanding the effect of maintenance_work_mem on time taken
> by CREATE INDEX, I observed that for the values of
> maintenance_work_mem less than the value for which an internal sort is
> performed,
On Wed, Jul 24, 2013 at 6:02 AM, Jeff Janes wrote:
> On Tue, Jul 23, 2013 at 1:23 AM, Amit Langote wrote:
>> On Tue, Jul 23, 2013 at 1:11 PM, Amit Langote
>> wrote:
>>> Hello,
>>>
>>> While understanding the effect of maintenance_work_mem on time take
On Wed, Jul 24, 2013 at 11:30 AM, Amit Langote wrote:
> On Wed, Jul 24, 2013 at 6:02 AM, Jeff Janes wrote:
>> If you are using trace_sort to report that, it reports the switch as
>> happening as soon as it runs out of memory.
>>
>> At point, all we have been doing is
On Wed, Jul 24, 2013 at 3:20 AM, Jeff Janes wrote:
> On Mon, Jul 22, 2013 at 9:11 PM, Amit Langote wrote:
>> Hello,
>>
>> While understanding the effect of maintenance_work_mem on time taken
>> by CREATE INDEX, I observed that for the values of
>> maintenance
development phase, but you could give it a try and see if it can
perform better where pg_trgm can not.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
7;t need to manually move any of the files in pg_xlog/,
PostgreSQL automatically gets rid of or recycles the files.
> 4. Do I need to backup the .backup files in the archive folder or just the
> 16,384KB WAL files?
>
Your archiving setup (that is archive_command) should take care of all
t
there shouldn't have been like 0010146A0001 instead of
000F146A0001. This patch recently applied to 9.1.9 (but
not in any stable release so far) solves this problem as far as I can
see. Try and see if you can patch it:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=424cc31a3785bd01108e6f4b20941c6442d3d2d0
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
DO location (identified as "START
WAL LOCATION:" field in the backup_label file.) While you are reading the
code, you can read the comment above the function read_backup_label()
in src/backend/access/transam/xlog.c
--
Amit Langote
tore and retrieve the indexed content using PostgreSQL.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi Jeff,
On Tue, Jul 30, 2013 at 3:25 AM, Jeff Janes wrote:
> On Tue, Jul 23, 2013 at 10:56 PM, Amit Langote
> wrote:
>> On Wed, Jul 24, 2013 at 3:20 AM, Jeff Janes wrote:
>>>
>>> The heap structure used in external sorts is cache-unfriendly. The
>>&
"pgbench -i -s 3500" would be.
May the routines in fd.c become bottleneck with a large number of
concurrent connections to above database, say something like "pgbench
-j 8 -c 128"? Is there any other place I should be paying attention
to?
--
Amit Langote
--
Sent via pgsql-
On Mon, Aug 5, 2013 at 5:01 PM, KONDO Mitsumasa
wrote:
> Hi Amit,
>
>
> (2013/08/05 15:23), Amit Langote wrote:
>>
>> May the routines in fd.c become bottleneck with a large number of
>> concurrent connections to above database, say something like "pgbench
the db. I'm trying to achieve that on
postgres.
I've configured the log_statement='all' in postgresql.conf.
Thanks
Amit
el query plans are logged.
http://www.postgresql.org/docs/devel/static/auto-explain.html
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
the primary server may be running multiple WAL senders,
there is only one WAL receiver on each standby server.
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Is
> that right?
>
Yes. It would be used for the duration of backup. But, it maybe better
to just reserve one slot for pg_basebackup if you intend to use it
often instead of editing postgresql.conf every time you need to take
backup.
--
Amit
--
Sent via pgsql-general mailing lis
Hi,
In 9.2 docs, the first link (i18ngurus) in the further reading section here:
http://www.postgresql.org/docs/9.2/static/multibyte.html
seems to be broken. Should it be updated/removed?
(I see it's removed in 9.3 docs)
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-ge
EATE TABLE
Time: 31.344 ms
postgres=# \dt
List of relations
Schema | Name | Type | Owner
+-+---+---
public | id_äß | table | amit
(1 row)
postgres=# SET client_encoding TO UTF8;
SET
Time: 1.007 ms
postgres=# \dt
List of relations
Schema |
On Tue, Oct 22, 2013 at 7:00 PM, Albe Laurenz wrote:
> Amit Langote wrote:
>> With a server initdb'd with UTF8 encoding , if I create a table with a
>> client using LATIN1 encoding and later try to work with the relation
>> with a client using UTF8 encoding (both the
maintenance_work_mem?
Or are these things unrelated?
--
Amit
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Thu, Oct 24, 2013 at 7:26 PM, Andres Freund wrote:
> On 2013-10-24 18:40:46 +0900, Amit Langote wrote:
>> While going through the documentation for GIN fast update technique, I read -
>>
>> "...or if the pending list becomes too large (larger than work_mem),
>&
rows)
-- You could go ahead and add more trigrams that you'd want result to contain.
postgres=# insert into foo values ('gabcddfg');
INSERT 0 4
postgres=# select * from foo where a LIKE '%abc%dfg%';
a
--
gabcddfg
(1 row)
Is this what you want?
--
Amit
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Thu, Nov 14, 2013 at 9:05 PM, Janek Sendrowski wrote:
> Hi Amit,
>
> Thanks for your answer.
>
> My issue is that I still need a ranking like the similarity when comparing
> trigrams.
> I'm working on a similarity search, which determindes similiar sentences from
nsistent
> recovery state reached at 4/32CCAA88
> [2013-12-19 04:14:33.909 CST 18332 52b2021c.479c 4 0]LOG: database
> system is ready to accept read only connections
> [2013-12-19 04:14:34.059 CST 18340 52b2021c.47a4 23 0]LOG:
> unexpected pageaddr 3/5A00 in log segme
ttp://www.postgresql.org/message-id/caaswcxe2rqx66wzw10kmehgb1c+hzwfeavvm-vprik6ppfa...@mail.gmail.com
http://www.postgresql.org/message-id/caaswcxekevpji03mjzdy6auo0x7quewx5yzqhsnp7gj1bao...@mail.gmail.com
http://www.postgresql.org/message-id/CAASwCXfgFsMt31c1srj=fszbz5cc3ahjckfu3kznxds7ogq...@mail.gmail.com
-
es, using random sampling), I guess you'd need to go through its
code in the source file "src/backend/commands/analyze.c".
--
Amit Langote
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
1 - 100 of 138 matches
Mail list logo
