s pretty
invasive, and that's not a bug if you think about it.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
s name in Linux binaries packages.
>
> Can someone please advise the equivalent library for postgres.lib in Linux?
There is no need to go down to this level of details perhaps? You
could just use the PGXS infrastructure to guess it for you.
--
Michael
--
Sent via pgsql-general mailin
y that if I recall correctly. But, anyway, what Kiran is looking
for here is to build his stuff via PGXS.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
of checkpoints triggered by volume. It
is difficult though to draw a conclusion without more idea about your
load, the WAL record generated, etc.
--
Michael
--
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 10, 2016 at 3:10 AM, nore...@evolu-s.it wrote:
> Someone else facing this problem?
Saw that a couple of times. Anti-virus softwares on Windows are known
to interact badly with Postgres instances if no filters are applied or
if they are kept around running.
--
Michael
--
Sent
trings generated by the server the way you want.
I wrote such a thing some time ago to generate logs with a JSON
format, you may want to look at that to give you more ideas:
https://github.com/michaelpq/pg_plugins/tree/master/jsonlog
--
Michael
--
Sent via pgsql-general mailing list (pgsql-gene
bits. This generates traffic for OLTP types of workloads where many
pages are dirtied and flushed at checkpoint.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e PITR
and restore to a position before the last segment available in its
timeline history.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ed. I would not want to reindex
> a table in OLTP env.
Like VACUUM FULL, don't forget that REINDEX needs an exclusive lock
when working. As that's very intrusive, usually you take measures on
your database to be sure that you *never* require it, particularly if
this is a production
g_rewind
does. Once a rewind completes, pg_rewind creates a backup_label file that
includes the real data used by the startup process to determine from which
segment replay will start. I think that you had better rely on its content
to check what is the first segment the new slave needs to replay and if it
is still present on the new master.
--
Michael
signature.asc
Description: PGP signature
found many cases where the
same customer has different first names in the two datasets. A sampling of the
differences is as follows:
Michael <=> Mike
Tom <=> Thomas
Liz <=> Elizabeth
Margaret <=> Maggie
How can I build a query in PostgreSQL (v. 9.6) that will find possibl
::cstring);
else
raise notice '%', to_regclass(myschema||'. '||mytable);
end if;
I wanted to confirm, is this the best way to approach this?
--
Michael Rasmussen
Sr. Data Engineer
Porch
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your s
-disk write pattern of data in pg_xlog is sequential
writes, while there will be likely random writes on the main data folder.
On top of that, moving them to a different partition gives more flexibility
in the way to tune checkpoint-related parameters using the partition space
as a constraint for retention policy and checkpoint timings.
--
Michael
signature.asc
Description: PGP signature
ates
> > pg_catalog when I create a new DB.
>
> This is because, in general, pg_catalog is maintained by DML
> statements, restoring it is not going to do what you think.
s/DML/DDL/
--
Michael
signature.asc
Description: PGP signature
oint to the new partition
> 4. restart PostgreSQL
Similar flow on Windows, just use a junction point for the link.
--
Michael
--
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, Nov 29, 2016 at 10:25:50AM -0200, Saulo Tadeu wrote:
> I'm would like to know which companies use postgres-XL and Postgres-BDR.
> Could you name some companies?
Usually companies are not willing to disclose information regarding the
infrastructure they are using.
behind?
WAL archives are kept up to date, meaning that all the segments older
than the one being written are archived (well perhaps not if the
archiver lags behind). wal_keep_segments numbers the number of
segments kept in pg_xlog past the last completed checkpoint.
--
Michael
--
Sent via pgsq
ll are the tools to use to restore a database
or multiple databases from a past state, and provides options
regarding what you want to dump. So go for it.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgr
and finally bring the sanitized data into
Postgres using the copy command.
So yes, character set and collations sets are the bane of DBAs, and yes, they
are a bitch to troubleshoot and yes, they often take very creative solutions to
fix.
Michael
> On Dec 7, 2016, at 4:40 AM, Maeldron T. wr
n limitation in Postgres that pg_rewind was written to
> address.
FWIW I maintain a version that works on 9.4:
https://github.com/vmware/pg_rewind
And that's battle-proven.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
as well as if that's a hardware problem, so you
are just seeing the beginning of a series of problems.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
void such corruption problems if
full_page_writes and fsync are enabled, that's a base stone of its
reliability. If you can create a self-contained scenario able to
reproduce a failure, that could be treated as a Postgres bug, but you
are giving no evidence that this is the case.
--
Michael
--
Sent
ient as SPI?
>
> No.
To give more details here, Postgres relies heavily on the fact that sessions
working in parallel on the backend should be done in separate processes,
like for transaction or snapshot handling.
--
Michael
signature.asc
Description: PGP signature
eate what autovacuum does with a
launcher process and workers created depending on what needs to be
cleaned up per database as a plugin.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
en relation get extends?
You need to look at smgrextend() when extension an on-disk relation
file. The page is written in a correct shape.
> If so what details it writes? Or will it be null?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
story files to
define a new timeline. If you rely only on streaming replication, only
9.3 and newer versions are able to do that: the replication protocol
has been extended at this point to allow a standby to fetch from a
primary history files.
--
Michael
--
Sent via pgsql-general mailing list
On Sun, Dec 11, 2016 at 7:31 PM, Torsten Förtsch wrote:
> Is it possible to catch CREATE TABLE and ALTER TABLE RENAME in 9.5?
You are looking for pg_ddl_command via event triggers.
src/test/modules/test_ddl_deparse is one example of that in the code
tree.
--
Michael
--
Sent via pgsql-gene
of the conversion.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
both can be done, but others disagree,
Event triggers could be used to track the creation or drop timestamp
of objects. Even if it is not supported for REFRESH, it may make sense
to support it in the firing matrix.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.
g/docs/9.6/static/protocol-message-types.html
If you are looking at a reliable way to re-implement the frontend-side
protocol parsing the information according to those docs is the way to
go.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
If you want an IDE, Jetbrains, the makers of great IDEs like IntelliJ, PyCharm.
and AppCode, among others, have recently come out with what is arguably the
BEST IDE for DBAs, DataGrip. It runs on most major platforms, and is so good
that I have bitten the bullet and paid the yearly subscription
get around postgres dependency issues.
>
> On Fri, Dec 30, 2016 at 1:40 PM, Michael Sheaver <mailto:mshea...@me.com>> wrote:
> If you want an IDE, Jetbrains, the makers of great IDEs like IntelliJ,
> PyCharm. and AppCode, among others, have recently come out with what is
>
SQL.
> Can anyone show me how to properly identify the problem with my backup? I am
> also worried that my backups are not being properly made.
You may want to see that with the maintainers of barman, they are
likely looking at this list. But here is a guess: the backup_label
file has been rem
NTENCODING?
And if anyone from the Postgres team listening... in the old tradition of
whining I would add that the error message referring to a long hex string is
not helpful!
Thanks in advance.
Michael.
This email and any attachments are intended solely for the use of the
individual or entity to
a checkpoint manually after promoting the
node to be sure that its control file gets the new timeline number.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thank you Torsten and Tom, this rang the bell and put me on the right track.
>> " This should be a can't-happen failure ..." - indeed, the wound is
>> self-inflicted.
Michael.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday,
;s
why, while it is important to take backups, it is more important to
make sure that they are able to restore correctly before deploying
them.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
g to expect a patch which adds more
> detailed stage 3 reporting? Say index number being vacuumed.
What would be more interesting would be like the heap to get
information on the index block being cleaned up with reports being
done via index_bulk_delete(). That's more work, and that would
On Tue, Jan 24, 2017 at 5:37 PM, Alexander Shchapov
wrote:
> On Tue, Jan 24, 2017 at 8:57 AM, Michael Paquier
> wrote:
>> What would be more interesting would be like the heap to get
>> information on the index block being cleaned up with reports being
>> done via ind
irectory containing the referencing file.
So you could take advantage of that to handle your configurations on
different nodes with the same pg_hba.conf, but different users and
databases.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your sub
goto 1
Craig, could this be a side-effect of 519b0757? That's new in 9.5, and
that's directly related to the code paths discussed here.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
rimary when they are waiting for the standby
to confirm that the transaction has been committed as well there,
before sending back confirmation to the client. So statement_timeout
has no effect on in such situations.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
or any attachment for any
> purpose, nor disclose all or any part of the contents to any other person.
This is a public mailing list.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
t four ones, you could use the query planner hook, here is an
example (don't use it btw, but feel free to get inspiration from it
for your stuff):
https://github.com/michaelpq/pg_plugins/tree/master/pg_panic
Regards,
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgres
On Wed, Nov 18, 2015 at 4:38 PM, Adrian Klaver
wrote:
>
>> Alright, I was following you up to this. Seems to me deleted data would
> represent stale/old data and would be less valuable.
>
>>
>>
It may depend on WHY the data was deleted. If it represented, say, Hillary
Clinton's deleted email, rec
ot;z":6} ] }]'::json) AS json_data;
keys
--
7
4
(2 rows)
That's a bit rough I agree but the correct functions wrapped with some
plpgsql or SQL could prove to be generic enough.
> Also is there a definition of the syntax of a proper json path for use in
postgres?
http://www.postgresql.org/docs/devel/static/functions-json.html
--
Michael
updating the slots on the master, not the standby. Even if the backup
is only intended for use in creating a new master, copying the
replication slots isn't expected to be particularly useful, since the
contents of those slots will likely be badly out of date by the time
the new master comes
he
server be stopped. That's less error handling to take care of at
frontend level.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
le_schema, new_table_name]::text[], but that had no effect.
Does anyone know what I might be doing wrong?
--
Michael Rasmussen
Sr. Data Engineer
Porch
||'_source', new_table_name||'_source']];
else
the_tables := array[[new_table_schema, new_table_name]];
end if;
--
Michael Rasmussen
Sr. Data Engineer
Porch
On 12/28/15, 3:51 PM, "Tom Lane" wrote:
>"David G. Johnston" writes:
>>
On Mon, Dec 28, 2015 at 2:08 PM, Christopher Molnar
wrote:
> Hello all!
>
> Sorry to have to ask the experts here for some regex assistance again. I
> am admittadly awful with these and could use some help.
>
> Any suggestions?
>
I have found over the years that it is far easier to write a short
On Fri, Jan 1, 2016 at 11:36 AM, Joshua D. Drake wrote:
> Welcome to 2016.
>
> Let's have another bang up year!
+1.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
27;__crt_locale_data'
I am afraid that's not within the support range now.. Like similar
builds with MSVC in the past, this is surely going to need some teaks
with _MSC_VER flags. Just nobody got around yet to patch the code.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-gener
al support. This email
> list is for the community open source version of PostgreSQL.
If you actually come up with a self-contained test case that fails
with the community version, then here would be fine.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
of 9.4 older than 9.4.5, right? Like 9.4.4?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ectly how get_db_and_rel_infos would get called twice for the same
connection.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
d the slave cannot replay from
the master as transactions are running on the hot standby.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ed with a code of
conduct, just something that each individual should try to solve by
himself. And IMHO, this would just complicate the contribution flow
and the life of people who could potentially provide something useful.
Folks on the mailing lists here are really cool and it is possible to
h
On Wed, Jan 6, 2016 at 9:27 AM, Yoji wrote:
> Hi Andreas and Michael,
>
> Thank you for your information!
>
> Let me know, which should I choose update to 9.4.5
Updating to 9.4.5 is highly recommended, and a separate issue.
> or hot_standby_feedback off?
Switching hot_stand
On Wed, Jan 6, 2016 at 4:29 PM, Mohammed Ajil wrote:
> What is an executor hook?
Here you go, with a particular focus on the ones names Executor*_hook:
https://wiki.postgresql.org/images/e/e3/Hooks_in_postgresql.pdf
--
Michael
--
Sent via pgsql-general mailing list (pgsql-gene
p are two independent things, the latter
being an independent facility and the in-core TAP tests do not need
it. If you want to run them, simply install the perl module IPC::Run
and add this configure switch: --enable-tap-tests.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-gen
re for long though so perhaps my
perception is incorrect), and in Japanese it just doesn't matter,
there is no such concept.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ould want to treat that as a bug fix
as nothing is broken, it looks more like a new feature.
> Any suggestions for a better way to accomplish the goal?
What I have been doing in such cases until now is updating the name of
the terminal tab to identify what was going on.
--
Michael
--
Sent
hout them.
> I ran ./configure --prefix=$HOME/project --enable-depend --enable-cassert
> --enable-debug and it seems to have completed with no errors, but I do not
> see anything at $HOME/project?
I would not think so, without bison in PATH ./configure would not
complete, and
ensed, title
> line would be nice though using two in order to not be cryptic has its own
> appeal.
Just looking at that I just hacked the attached that enforces \n at
the end of the user-defined title (that's easily changeable):
=# \pset title 'foo bar'
Title is "foo bar&q
quot; does not exist
Environment:
CentOS 6.6
postgresql91-server-9.1.14-1PGDG.rhel6.x86_64
Thanks,
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
27;t exist without a relation to apply it to.
Michael
On Wed, 2016-01-13 at 15:08 -0800, Adrian Klaver wrote:
> On 01/13/2016 02:51 PM, David Rowley wrote:
> > On 14 January 2016 at 11:32, Adrian Klaver om
> > <mailto:adrian.kla...@aklaver.com>> wrote:
> &
; from contrib to src/test/modules, which means they won't get installed in
> standard installations.
Additional note: on Windows when code is compiled with MSVC, they are installed.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to yo
nted structures)
How long do you think it would take for MS 1820 to be fixed and out? I
wouldn't personally mind telling to people trying to compile with 1800
that we cannot support it because it is buggy. That's one less wart to
have forever in the code.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
get that?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Wow, thanks for doing that!
>>
>
> Yes, no doubt. Can we get this linked somewhere so we don't lose it?
Here would be fine, no?
https://wiki.postgresql.org/wiki/Detailed_installation_guides
There is a section for Windows.
--
Michael
--
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, Jan 26, 2016 at 10:34 AM, Joshua D. Drake
wrote:
> On 01/25/2016 05:29 PM, Michael Paquier wrote:
>>
>> On Tue, Jan 26, 2016 at 3:56 AM, Joshua D. Drake
>> wrote:
>>>
>>> On 01/25/2016 10:49 AM, Joshua Berkus wrote:
>>
ed so what do you
think about that instead?
Watch every Xs $timestamp
$head_title
--
Michael
--
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, Jan 28, 2016 at 1:54 PM, David G. Johnston
wrote:
> On Wed, Jan 27, 2016 at 9:13 PM, Michael Paquier
> wrote:
>>
>> On Thu, Jan 28, 2016 at 9:34 AM, David G. Johnston
>> wrote:
>> > So how about:
>> >
>> > + snprintf(title, strlen(my
length title
repeat
--
aaaaaaaa
(1 row)
--
Michael
emit transaction command such as BEGIN, ROLLBACK
and COMMIT. Thus, all SQL statements are executed in each transaction when
'autocommit' was set to 'on'.
What is the correct state of the subject?
--
Regards,
Michael Holzman
On Mon, Feb 8, 2016 at 6:25 PM, Adrian Klaver wrote:
> What is the correct state of the subject?
>
> The documentation.
>
> If you look a bottom of Wiki page you will find:
>
> This page was last modified on 6 March 2012, at 11:11
>
> --
> Adrian Klaver
>
ts and similar stuff.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
the complete error message that you think is a bug?
--
Michael
e with the PostgreSQL license. If you plan to maintain that
as an independent project that would never be integrated with Postgres
directly, the license does not really matter, but it would prevent
other people to do the integration legwork into core if having your
feature makes sense.
--
Michael
--
On Fri, Feb 12, 2016 at 4:29 AM, Oleg Bartunov wrote:
> Похоже на то, что вы понимаете по-русски !
I don't. My bad.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
016.pgday.asia/index.html#stayinginformed
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
at transaction level for example by disabling
synchronous_commit.
Regards,
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
_standby_names = 'keypg2,*'
This is fine. Thanks to '*', all the other standby nodes connected to
this primary server will be thought as potential synchronous
candidates. And one of them will be. With this configuration keypg2 is
chosen first though if it is connected.
--
Micha
warm may help as well. This has the advantage to not rely on
oid2name or similar for the relation selectivity.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
on-to-be-standby has a minimum recovery target sufficient. You had
better use it.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
the target node before performing the rewind.
> Maybe a note about it should be added to the wiki
> https://wiki.postgresql.org/wiki/Streaming_Replication
> (not sure if I can)
With a community account you could edit this page.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-
f them are managed with systemd? Are there differences
in each one's spec file, I find rather bad the fact that there is
something removing the semaphores at OS level all-of-a-sudden.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
not at the point where WAL
forked, but from the previous checkpoint record before WAL forked.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
an this query, and
what is the version of libpq used on client-side, which may not be
from 9.5.0. Compatibility is ensured with the protocol 3, so that
should work anyway.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I should have noted: the application is using PostgreSQL 9.5.0, running on
Ubuntu 14.04
Mike
On Fri, Mar 18, 2016 at 10:41 AM, Michael Charnoky wrote:
> Hi, I'm seeing random errors from an application that is performing DB
> inserts. The error happens spuriously and looks like th
Hi, I'm seeing random errors from an application that is performing DB
inserts. The error happens spuriously and looks like this from the
application side:
could not open file "/dev/shm/postgres_apptable_47861701461760" for
reading: No such file or directory
The PostgreSQL logs show:
2016-03-18
d the CF record and forgot:
>> https://commitfest.postgresql.org/9/480
>> It was added 2016-01-13 by Michael Paquier.
>
> OK, so it looks like David's 10-Mar patch was actually just a repost of
> Michael's 28-Jan patch, which was already in the queue to be reviewed in
>
On Mar 18, 2016 10:59 AM, "Tom Lane" wrote:
> Offhand I do not believe that any part of the core PG code would attempt
> to access such a file. Maybe you've got some extensions in there that
> would do so?
Thanks Tom, thought this was a PG issue. I'll dig more into the guts of the
application
hange the return statement at the bottom of the function to
> return (res != -1).
OK.
And the patch attached gives the following output:
With title:
=# \watch 1
Watch every 1sSun Mar 20 22:28:38 2016
popo
a
---
1
(1 row)
And without title:
Watch every 1sSun Mar 20 22:29:31 2016
a
--
On Tue, Mar 22, 2016 at 6:25 AM, Tom Lane wrote:
> If I don't hear objections PDQ, I'm going to update the docs and commit
> it like that.
Thanks!
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://ww
ata directory?
That's likely the reason, something creeping behind is forcing
disconnections from the server.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
He asked a legitimate question. Why he wants to hide the code is his business.
If you don't know the answer, or don't want to tell him, don't answer.
Michael Milligan
he error come from the WAL receiver, you would have something like that.
FATAL: could not receive data from WAL stream: ERROR: requested WAL
segment 0001001C has already been removed
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chan
I'm looking at the possibility of using JSON as a data exchange format
with some apps running on both PCs and Macs. .
The table I would be exporting has a lot of NULL values in it. Is
there any way to skip the NULL values in the row_to_json function and
include only the fields that are non-null
201 - 300 of 3411 matches
Mail list logo
