Re: [GENERAL] Pgadmin access to Postgresql

r local TCP connections not remote ones. You typically want listen_addresses set to "*" if you intend to allow remote connections. When you start getting complaints phrased along the lines of "no pg_hba.conf entry" then it'll be time to fix pg_hba.conf.

Re: [GENERAL] error when upgrading 9.4 to 9.5 manually

pg_upgrade -b /usr/lib64/pgsql/postgresql-9.4/bin -B /usr/bin -d > /db/pgsql/data.old -D /db/pgsql/data Why are you not using "postgresql-setup upgrade", as documented in /usr/share/doc/postgresql-NNN/README.rpm-dist ? regards, tom lane -- Sent vi

Re: [GENERAL] error when upgrading 9.4 to 9.5 manually

o a conclusion not supported by this evidence; we can't tell whether the postmaster started at all. Did you look into pg_upgrade_server.log as suggested? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Slow SQL?

subselects seem to be pretty expensive. If you don't want to rewrite the query in a wholesale fashion like he suggests, you might be able to make the MAX's cheaper by providing an index on sed_uttak(avlsnr, dato); but I'm not sure how much that will help. re

Re: [GENERAL] Question about antijoin

culations, but we leave it to * distribute_qual_to_rels to get rid of such clauses. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] pg_restore out of memory

ompiled to get 32kB blocks 9.1.8 is pretty old ... regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Upsert with a partial unique index constraint violation

> That should work. Are you sure you haven't spelled it "... WHERE d IS TRUE"? It does work for me, but I think it probably only started working after this as-yet-unreleased patch: Author: Tom Lane Branch: master [26e66184d] 2016-05-11 16:20:23 -0400 Branch: REL

Re: [GENERAL] pg_restore out of memory

Miguel Ramos writes: > Às 15:40 de 12-07-2016, Tom Lane escreveu: >> Unless you're running pg_restore under a really small ulimit, this would >> seem to suggest some kind of memory leak in pg_restore itself. I wonder >> how many objects in your dump (how long

Re: [GENERAL] pg_restore out of memory

at is being worked on when the error happens. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] PostgreSQL FDW + Trigger on Remote DB = WARNING: there is no transaction in progress

plete example for anyone to diagnose it. Also, what PG versions are in use exactly, both local and remote? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] pg_restore out of memory

at's a contributing factor. I'm still suspicious that this might be some sort of NOTICE-processing- related buffer bloat. Could you try loading the data with the server's log_min_messages level cranked down to NOTICE, so you can see from the postmaster log whether any NOTICEs are

Re: [GENERAL] postgresql "init script" for postgres 9.2.15

to in the scripts you already have. You may spend more time dealing with useless-to-you changes than you save by not doing your own research on what changed in Postgres. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) T

Re: [GENERAL] pg_restore out of memory

or across a network --- and if the latter, how fast is the network? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Server side backend permanent session memory usage ?

derr (hopefully you are starting the postmaster in such a way that that gets captured to a log file rather than sent to /dev/null). Save that. Wait until you see bloat, reattach and repeat, compare the memory maps. Let us know what you see. If possible, compare maps taken at points where the sess

Re: [GENERAL] Trouble starting Postgresql after an upgrade

somewhere, else you'd not have gotten this far. > To make the problem more interesting, I can bring the DB engine up if I use > pg_ctl … but only if I’m in the data dir. Possibly you have "data_directory = ." or something like that in the config file? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] pg_restore out of memory

ith log_min_messages to 'notice'. OK. > I suppose log_statement to 'all' is no longer necessary? I agree; we already know which statement is failing. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] migrating data from an old postgres version

ot;--quote-all-identifiers" was invented to address. But if you don't use that option, you're at risk for that regardless of whether you dumped with the older or new pg_dump. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.

Re: [GENERAL] Recovering data from an old disk image

on our webservers, but in any case you could easily check out that tag from our git server to recover the matching source code. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Constraint using a SQL function executed during SELECT

obvious showstoppers like a FROM clause. This wouldn't constitute a general solution to your problem, of course, but it would save some useless cycles in planning. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Is it possible to control the location of the lock file when starting postgres?

o put the socket) as the host location. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Multiple clusters with same tablespace location

n setting up new slave instances, pg_basebackup's --tablespace-mapping option would help you with that. For an existing slave instance, you'd need to shut it down while manually moving the tablespace directory(s) and re-pointing the symlink(s). regards, tom l

Re: [GENERAL] pg_dump without any SET command in header of output plain text sql file

Alex Ignatov writes: > Is there any way to make pg_dump(9.5) to dump table (with data) without > any SET command in the header of output plain sql file? No, but if all you want is the table data in a file, why not just use COPY? regards, tom lane -- Sent via

Re: [GENERAL] 9.5: pg_stat_statement and pgbench execution time discrepancies

ts only measures the executor runtime, omitting parse/plan times as well as network transmission times. pgbench is reporting the overall time as seen from the client side. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make

Re: [GENERAL] gin index operator class functions in sql?

Andrew Geery writes: > Is it possible to define functions in SQL (as opposed to C) to do the same > thing -- create an operator class -- for a gin index? Afraid not; several of those APIs are C-specific. regards, tom lane -- Sent via pgsql-general mailing list

Re: [GENERAL] A simple extension immitating pg_notify

it'd be impossible to have clean semantics for failures: the sending transaction would have committed all right, but some of the recipients wouldn't get the notification. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] A simple extension immitating pg_notify

action commits. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Weirdness with the stats collector process

ce? You could at least confirm whether it's receiving anything. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] question on parsing postgres sql queries

IN. It might be nice to have some sort of tool that could check compatibility of the doc synopses with the actual grammar. But I doubt that trying to auto-generate either one from the other would be a win. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-ge

Re: [GENERAL] Weirdness with the stats collector process

e when PG wasn't running, but it was pretty foolish to do it to a running system without even looking to see if any IPV6 connections were open :-( regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] How to give complete ownership of a new DB to a new user (non-SU)?

e drudgery out of it, if you have the template database set up properly. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Server side backend permanent session memory usage ?

ps://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=1d2fe56e4 We did not back-patch those changes because they seemed rather invasive/risky compared to the value for average users. If you still see misbehavior in 9.6, it'd be worth trying to extract a self-contained exa

Re: [GENERAL] Multiple NOTIFY is ignored

;0|UPDATE|A|" received from server process with PID 19442. Asynchronous notification "foo" with payload "0|DELETE|A|" received from server process with PID 19442. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] 9.6beta3

or pg_upgrade for the new version anyway because of other catalog changes. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Proposal "stack trace" like debugging option in PostgreSQL

like "duplicate key" (or a function raise exception) or > other similar problems that wont allow the database to execute the SQL > command,the strack trace will bring the complete list of function call. Uh, doesn't the CONTEXT field of error messages give you that already?

Re: [GENERAL] Proposal "stack trace" like debugging option in PostgreSQL

ifoo($1,$2)" PL/pgSQL function ifoo2(integer,text) line 1 at PERFORM STATEMENT: select ifoo2(1,'foo'); regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Force pg_hba.conf user with LDAP

enefit of approaching things this way is it doesn't have to be all-or-nothing: the gating function can apply checks on what it will allow. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: ht

Re: [GENERAL] Re: Query planner using hash join when merge join seems orders of magnitude faster

is happening or not. It'd manifest as one join input node showing an actual number of rows returned that's less than you'd expect. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Commands history with psql in a Windows command line shell

e may not be any version that works well. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Problem with partitioning

on updates to rows in the child tables. To get that effect, attach the same trigger procedure to all the children. Don't recall offhand what the rules are for per-statement triggers. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@post

Re: [GENERAL] connection file descriptors created with identical number after process fork on mac

re process-local in all flavors of Unix. The above only proves that all of these processes had FDs 0..12 open already, which doesn't seem terribly surprising. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes

Re: [GENERAL] fun fact about temp tables

;s any need to push the data out of shared_buffers. Otherwise, you might find yourself having to throw an "out of disk space" error after having already committed the relevant INSERTs. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgre

Re: [GENERAL] fun fact about temp tables

k-space while flushing a buffer, that's what we'd risk. So we allocate the disk space before accepting the INSERT in the first place. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] fun fact about temp tables

Alex Ignatov writes: > On 05.08.2016 17:51, Tom Lane wrote: >> Sure. Just like it reserves space for ordinary tables right away, >> long before there's any need to push the data out of shared_buffers. >> Otherwise, you might find yourself having to throw an "ou

Re: [GENERAL] Detecting if current transaction is modifying the database

gh I do not think they're exposed at the SQL level. > Another thing I should have mentioned is that I don't consider incrementing > a sequence to be a modification. Things might not work the way you want on that... regards, tom lane -- Sent via pgsql-general m

Re: [GENERAL] Should a DB vacuum use up a lot of space ?

hours). Why is that ? Probably because there's no background process to issue auto-checkpoints and thereby recover WAL space. I'd try doing a control-C on the VACUUM, then a CHECKPOINT, then start over. You might have to vacuum large tables individually and checkpoint after ea

Re: [GENERAL] how to serialize insert followed by read(select) by different clients

s and COMMITs get issued. (Well, I guess that only exhausts the possibilities as long as this is happening on a single database server. If the reader is reading from a hot-standby slave then replication delays might explain your problem. But that would be a rather material omission of fact

Re: [GENERAL] lower() silently fails for 9.5.3 on Windows, but works on Mac, Linux

will be transformed by upper/lower. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] select array_length(array_remove(ARRAY[NULL,NULL,NULL],NULL), 1); returns NULL instead of 0

egards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] select array_length(array_remove(ARRAY[NULL,NULL,NULL],NULL), 1); returns NULL instead of 0

Alexander Farber writes: > Thank you, so should I maybe switch to cardinality then? Yeah, that should work. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailp

Re: [GENERAL] Column order in multi column primary key

ml Having said that, I'm pretty skeptical of the notion of redefining what your PK is on performance grounds. With this definition, you'd allow two entries with the same work_session_id, if they chanced to have different customer_ids. Is that really OK? reg

Re: [GENERAL] select array_remove(ARRAY[NULL,NULL,NULL],NULL); returns {} instead of {NULL,NULL,NULL}

l) implements "IS NOT DISTINCT FROM" semantics rather than "=" semantics. I dunno that we want to make the documentation use that wording though, it'd probably confuse more people than it helped. regards, tom lane -- Sent via pgsql-general ma

Re: [GENERAL] Jsonb extraction very slow

ue available to look at. You could possibly alleviate some of the speed issue by storing the column uncompressed (see ALTER TABLE ... SET STORAGE EXTERNAL), but that would bloat your disk space requirements so I'm not really sure it'd be a win. regards, tom lane -

Re: [GENERAL] Detecting if current transaction is modifying the database

es both an XID and WAL entries. The same goes for most database alterations, really. There are very limited cases where you can produce WAL without assigning an XID or vice versa, but I'm not sure it's worth your while to distinguish. regards, tom lane --

Re: [GENERAL] plpython.h not installed in 9.4

ransform modules. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Jsonb extraction very slow

Jim Nasby writes: > I never dug into why. As Tom posited, decompression might explain the > time to get a single key out. Getting 10 keys instead of just 1 wasn't > 10x more expensive, but it was significantly more expensive than just > getting a single key. What were you

Re: [GENERAL] Jsonb extraction very slow

Jim Nasby writes: > On 8/11/16 8:45 AM, Tom Lane wrote: >> What were you doing to "get ten keys out"? If those were ten separate >> JSON operators, they'd likely have done ten separate decompressions. >> You'd have saved something by having the TOAST da

Re: [GENERAL] endash not a graphic character?

7;m not sure if any of the subsequent work on the regex engine would make it any easier to fix than it seemed at the time. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Unique constraint on field inside composite type.

t it got me to thinking, so: You'd need additional parens around the whole thing, like create unique index on "user"(((google_user).email)); The UNIQUE-constraint syntax will never work, because per SQL standard such constraints can only name simple columns. But you can make a unique

Re: [GENERAL] Permissions pg_dump / import

e same set of users as the source. Or just ignore these errors. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] pg_hba.conf : bad entry for ADDRESS

e this. But I think the problem is that you're required to specify a netmask or masklen; so "127.0.0.1/32" not just "127.0.0.1". regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your su

Re: [GENERAL] Understanding Postgres Memory Usage

If the same query, repeated over and over, causes memory to continue to grow, I'd call it a leak (ie bug). If repeat executions consume no additional memory then it's probably intentional caching behavior. regards, tom lane -- Sent via pgsql-general mailing

Re: [GENERAL] Understanding Postgres Memory Usage

ouching more and more of the shared buffer arena. (If your shared_buffers settings is not somewhere near 100MB, then this theory breaks down.) It would be worth using plain old top to watch this process. We have enough experience with that to be pretty sure how to interpret its numbers: "RES mi

Re: [GENERAL] Understanding Postgres Memory Usage

derr directed to a file, not to /dev/null.) That would provide a better clue about what's eating space. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Understanding Postgres Memory Usage

pathological behavior. Can you put together a self-contained test case? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Understanding Postgres Memory Usage

ade. Or I guess you could turn off enable_hashagg when using array_agg() plus GROUP BY, though you'd want to remember to undo that whenever you do upgrade. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes t

Re: [GENERAL] a column definition list is required for functions returning "record"

> How would you recommend to fix my declaration problem please? I think you are looking for the RETURNS TABLE syntax. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Error Upgrade PostgreSQL 9.4 to 9.5 in Debian

getting taken as arguments, not quotes. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] a column definition list is required for functions returning "record"

do is, eg, regression=# select * from plr(23,45); ERROR: a column definition list is required for functions returning "record" LINE 1: select * from plr(23,45); ^ because the parser has no basis on which to expand the "*". The column definition list is exac

Re: [GENERAL] UUIDs & Clustered Indexes

so why? A plain old bigint column is smaller, cheaper to index, and the natural mechanism for generating it (ie a sequence) will tend to preserve ordering for free. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to

Re: [GENERAL] UUIDs & Clustered Indexes

at most other browsers don't present that message :-( regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Array element foreign keys

nothing new has been submitted, I wouldn't hold my breath. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] PG_MODULE_MAGIC issue with small extension

an 8.* headers. Hm, where are you reading that? I forget when the requirement was added, but it's certainly never been dropped. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] PG_MODULE_MAGIC issue with small extension

bably not understanding the significance of this warning. I think what's wrong is you have not #include'd "fmgr.h" which is where PG_MODULE_MAGIC is defined. It's not exactly clear to me why that's resulting in a warning rather than an error, but certainly this is indic

Re: [GENERAL] RETURNS TABLE function returns nothingness

s exactly zero impact on the number of rows produced; it just stops execution. I think you can say RETURNS RECORD with a few OUT parameters to get the effect you're looking for. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.or

Re: [GENERAL] error initializing the db

161817.go1...@alvh.no-ip.org which would suggest that you're trying to build some fairly old PG version with some fairly new C compiler. Whether that's actually the case, well, you didn't give enough info to tell. regards, tom lane -- Sent via pgsql

Re: [GENERAL] Get date timestamp(3) without time zone column - PGSQL 9.5

;2016-08-10') > but it doesn't work.. I get 0 rows... what am I doing wrong? Are you sure you're not getting an error? The query is specifying fields in "tasks" but the FROM clause only lists "jobs". Either one of those two cast-to-date syntaxes should work, so

Re: [GENERAL] postgres question: Views with duplicate field names

x27;t do "create table foo (f1 int, f1 int)". They can be reading the same values, though. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Privileges on public schema can't be revoked?

member of PUBLIC. IOW, revoke only revokes a previous matching grant, and there was no such grant in this case. What there was was a grant to PUBLIC; see the relevant bit in initdb.c: "GRANT CREATE, USAGE ON SCHEMA public TO PUBLIC;\n\n", regar

Re: [GENERAL] Privileges on public schema can't be revoked?

idn't last I heard, I might be out of date.) regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Passing varchar parameter to INTERVAL

;, 'attacking other > users'); Hm? That would be passing a timestamp not an interval. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] a column definition list is required for functions returning "record"

initely has lots to recommend it --- eg, it probably won't break when you find out your initial spec for the transport format was too simplistic. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your su

Re: [GENERAL] How to assemble all fields of (any) view into a string?

or that, it just hasn't gotten the love the other PLs have. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] londiste re-create leaf node

ined symbol: oid_hash Looks like you built against a set of backend headers that is older than the server you're trying to run in. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Trigger is not working for Inserts from the application

es from applications because they invariably drop notices on the floor. I'd try RAISE LOG instead, and again watch the server log to see what the application is really doing. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make c

Re: [GENERAL] Trigger is not working for Inserts from the application

r trigger undoing its work? (psql's \d command on the table should show these things.) regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Trigger is not working for Inserts from the application

2}, {"labeltext": > "Other", "labelvalue": 3}, {"labeltext": "Don''t know", "labelvalue": 4}], > "target": {"place": "Sweden"}, "askfreq": "once", "whydesc

Re: [GENERAL] Duplicate data despite unique constraint

x27;; You definitely want to reindex after the data cleanup, since presumably it's corruption of a unique index that got you into this mess in the first place. But as long as it's only the index and not the table that's damaged, recovery is pretty straightforward.

Re: [GENERAL] Server crashed, now cannot start postgres

ollixed? As a temporary workaround, you could probably set dynamic_shared_memory_type = none in postgresql.conf (I'm assuming it's set to posix now). I do not think that disables any very critical functionality in 9.5, but it's a hack not a solution. rega

Re: [GENERAL] Server crashed, now cannot start postgres [FIXED]

t've had issues with setting this up wrong, but anything in current support ought to get it right ... regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Maximum number of exclusive locks

ther shared structures that grow at runtime. So there's room for the lock table to grow a bit beyond its nominal capacity. Having said that, the amount of slop involved is only enough for a few hundred lock entries. Not sure how you're managing to get to nearly 2 extra entries.

Re: [GENERAL] Maximum number of exclusive locks

Jeff Janes writes: > On Tue, Sep 13, 2016 at 6:21 AM, Tom Lane wrote: >> Having said that, the amount of slop involved is only enough for a >> few hundred lock entries. Not sure how you're managing to get to >> nearly 2 extra entries. > The code assumes ev

Re: [GENERAL] Request to share information regarding postgresql pg_xlog file.

successful checkpoint, that will take quite a while, so it's a last resort ... but it ought to work. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] ERROR: could not read block 4 ...

0 and re-create it from template1. Otherwise, pg_dumpall/initdb/reload would seem to be called for. A cautious person might want to do the latter anyway in case there's more problems than just this one. regards, tom lane -- Sent via pgsql-general mailing list (pgs

Re: [GENERAL] performance problems with bulk inserts/updates on tsrange with gist-based exclude constrains

but I would not be surprised if having lots of those is pretty destructive to the index's ability to be selective about && searches. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Unstable C Function

here are some other things I could criticize here, like labeling the function IMMUTABLE when its results depend on table contents, but they probably aren't causing your crashes. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To

Re: [GENERAL] Unstable C Function

Ian Campbell writes: > Thanks for personally replying, Tom. I appreciate it. > You are correct. In the interim, I found the following change solved the > issue: > SPI_finish(); // move to here > SRF_RETURN_DONE(funcctx); That might work under light usage, but the problem wi

Re: [GENERAL] Unstable C Function

he second arrival would get a SPI_ERROR_CONNECT failure from SPI_connect when there's already an open connection. For the nested- calls case you can prevent that with SPI_push/SPI_pop around a call that might wish to use SPI, but that fix doesn't work in a coroutine situation.

Re: [GENERAL] Question on replace function [solved]

Charles Clavadetscher writes: > Honestly I still don't understand why this happened this way. I wonder if you have standard_conforming_strings turned off, or did when that data was inserted. That would change the behavior of backslashes in string literals. rega

Re: [GENERAL] Chante domain type - Postgres 9.2

trace to crystal-clear application requirements. varchar(n) where n has been plucked from the air is a good sign of bad database design. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://ww

Re: [GENERAL] Stats update difference between VACUUM ANALYZE and ANALYZE in 9.2?

that you skipped ANALYZE'ing the partition parent tables in your first pass, but I'm betting on the all-visible fractions as being the issue. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

<    1   2   3   4   5   6   7   8   9   10   >